From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 602D83875B63; Tue, 6 Dec 2022 15:50:56 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 602D83875B63 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1670341856; bh=lzez8YJS0Lmh9HNqgsq226Z5kf7WPb5IFGcQuCEi238=; h=From:To:Subject:Date:In-Reply-To:References:From; b=C79qW3usXaegt3sPqscInV1abxmCntMGDIycBzRms2dnaT2jd6MF4kbzMfrUUFPAI +rXOf9giZQPJQ//jYL8jj5IgQfh7EAPRkrhiubb8QoD4xaw0wTaqiJaKn9Z4iye71x VjqiGuCeQSrrhH2AT+H6RqLqMI7lwESqLLFNjqTc= From: "glaubitz at physik dot fu-berlin.de" To: glibc-bugs@sourceware.org Subject: [Bug libc/23960] [2.28 Regression]: New getdents{64} implementation breaks qemu-user Date: Tue, 06 Dec 2022 15:50:54 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: libc X-Bugzilla-Version: 2.28 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: glaubitz at physik dot fu-berlin.de X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: security- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://sourceware.org/bugzilla/show_bug.cgi?id=3D23960 --- Comment #73 from John Paul Adrian Glaubitz --- (In reply to Adhemerval Zanella from comment #72) > (In reply to John Paul Adrian Glaubitz from comment #71) > > (In reply to Adhemerval Zanella from comment #70) > > > (In reply to John Paul Adrian Glaubitz from comment #69) > > > > For anyone else running into this problem: > > > >=20 > > > > The issue can be worked around by putting the target chroot onto a = btrfs > > > > filesystem. > > >=20 > > > Does it still fail with my patches applied? > >=20 > > It used to work with your patches, but that no longer seems to be the c= ase > > which I find strange. >=20 > Do you have any information of what might be failing? It would be good to > know if this is another non-LFS interface pitfall. I can only say at the moment that it occurs with Java applications even with your patches applied. For example, when running the "ant" command inside an emulated m68k chroot,= I am getting the following error: root@nofan:/# ant -version Failed to locateorg.apache.tools.ant.Main ant.home: /usr/share/ant Classpath: /usr/share/ant/lib/ant-launcher.jar Launcher JAR: /usr/share/java/ant-launcher-1.10.12.jar Launcher Directory: /usr/share/java root@nofan:/# When working correctly - which is the case on btrfs and xfs, for example - = the output looks like this: (sid-m68k-sbuild)root@z6:/# ant -version Apache Ant(TM) version 1.10.12 compiled on July 11 2022 (sid-m68k-sbuild)root@z6:/# --=20 You are receiving this mail because: You are on the CC list for the bug.=