Re: r238860: bsdtar: eating up 100% CPU, hanging

Do you know what the value of acl_tag is at this point?

On Jul 28, 2012, at 11:30 PM, Martin Matuska wrote:

> I am also looking into it:
>=20
> 1. It happens only with libarchive 3.0.4 (3.0.3 works fine)
> 2. It happens only if archiving files located on ZFS (UFS works fine)
> 3. Backtrace:
> #0  setup_acl_posix1e (a=3D0x801c45100, entry=3D0x801d69100, =
acl=3D0x801d8a000,
>    archive_entry_acl_type=3D256)
>    at
> =
/base/head/lib/libarchive/../../contrib/libarchive/libarchive/archive_read=
_disk_entry_from_file.c:474
> #1  0x0000000800879036 in archive_read_disk_entry_from_file =
(_a=3D0x801c45100,
>    entry=3D0x801d69100, fd=3D6, st=3DVariable "st" is not available.
> )
>    at
> =
/base/head/lib/libarchive/../../contrib/libarchive/libarchive/archive_read=
_disk_entry_from_file.c:434
>=20
> This infinite loop has been fixed in libarchive master:
> https://github.com/libarchive/libarchive/commit/d8b9dbd
> d8b9dbd6dac0125957b997c2fe8d246237ec9f94
>=20
> I suggest you backport to release also the following:
> f67370d5c33b336b103c43fe35984defe7e0e473
> https://github.com/libarchive/libarchive/commit/f67370d
> c6d3cd33aecdc579966c3fbe7b9424cea83c7555
> https://github.com/libarchive/libarchive/commit/c6d3cd3
>=20
>=20
> D=C5=88a 29. 7. 2012 3:18 Tim Kientzle  wrote / nap=C3=ADsal(a):
>>=20
>> On Jul 28, 2012, at 10:21 AM, O. Hartmann wrote:
>>=20
>>> When updating ports (like databases/sqlite3 or graphics/png via =
portmaster graphics/png), the installation process comes to a point =
where a backup of the old port is created with bsdtar. The process hangs =
then =E2=80=A6
>>=20
>>> My operating system is
>>> FreeBSD 10.0-CURRENT #0 r238860: Sat Jul 28 11:28:38 CEST 2012
>>=20
>> That's newer than my -CURRENT system here; I'm updating now.
>> Martin imported a few changes from upstream just recently, so this
>> is likely a new problem.
>>=20
>>> What to do?
>>=20
>> Can you get the full command line for the command that's
>> hanging?
>>=20
>> $ ps auxww | grep tar
>>=20
>> Knowing the exact options that were used will help narrow
>> it down.
>>=20
>> Thanks for reporting it,
>>=20
>> Tim
>>=20
>> _______________________________________________
>> freebsd-current@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to =
"freebsd-current-unsubscribe@freebsd.org"
>>=20
>=20
>=20

_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"