From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 45769398EC16; Fri, 2 Oct 2020 23:06:44 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 45769398EC16 From: "tg at mirbsd dot de" To: glibc-bugs@sourceware.org Subject: [Bug libc/23960] [2.28 Regression]: New getdents{64} implementation breaks qemu-user Date: Fri, 02 Oct 2020 23:06:43 +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: tg at mirbsd dot 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 X-BeenThere: glibc-bugs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Glibc-bugs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2020 23:06:44 -0000 https://sourceware.org/bugzilla/show_bug.cgi?id=3D23960 --- Comment #65 from Thorsten Glaser --- >I agree and this an overlook from we glibc maintainers to allow newer >32-bit ABIs to support non-LFS interface. Indeed. (Again, from a BSD PoV, wondering why this is so at all.) >Current pratice now is to enforce 64-bit >off_t for all newer ABIs (for instance as done for arc and riscv32). Good. >However, there are still legacy ABIs which supports non-LFS and even >one that support without having the legacy kernel interface (nios2 and >csky for instance). Ouch. That=E2=80=99s going to be tricky to fix. But enabling LFS on architectures that support n=C5=8Dn-LFS breaks so it=E2=80=99s not a generally usable fix either. ---- >In the mean time, I agree, you could make a mapping table for the rare >cases where telldir and seekdir are actually used. Can you make the linker choose a readdir implementation based on the presence of any of telldir and seekdir? Perhaps something with putting a readdir that just does its job, declared weak, into one archive, and a single .o containing telldir, seekdir, and a readdir that also maps 64-bit to 32-bit values into another, so that the latter is only chosen if telldir/seekdir are actually called? (AIUI it=E2=80=99s even only needed if *seek*dir is actually called, right?) --=20 You are receiving this mail because: You are on the CC list for the bug.=