From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: libc-alpha@sourceware.org
Subject: time64 / Large File Support: 1) [2.28 Regression]: New getdents{64} implementation breaks qemu-user
Date: Thu, 26 Jan 2023 00:58:41 +0100 [thread overview]
Message-ID: <6847475.SvYEEZNnvj@pinacolada> (raw)
In-Reply-To: <10857996.18pcnM708K@pinacolada>
[-- Attachment #1: Type: text/plain, Size: 2208 bytes --]
> 1) qemu usermode emulation is broken when emulating a 32bit arch from a 64bit
> arch, bug 23960
This is bug 23960 [2] on the sourceware bugzilla. As you can see it's been around
for a bit, and breaks emulating a 32bit architecture on a 64bit architecture.
Fear not, there is a fix, a patchset by Adhemerval Zanella [3]. It's been part of
Gentoo's glibc for several years now, solves the problem fully, and has
not led to any problems.
(We are in Gentoo Release Engineering heavy qemu usermode emulation users, building
for riscv, mips, loongarch64, m68k, alpha...)
Pre-2.37 the patchset stopped applying. To my best knowledge the
azanella/bz23960-dirent branch [4] provides an updated version. I tried to
verify that with Adhemerval, however unfortunately he never replied to my
pings on IRC, so that confirmation is still missing.
* Is that the current fix?
* Can we please merge it?
[2] https://sourceware.org/bugzilla/show_bug.cgi?id=23960
[3] https://gitweb.gentoo.org/fork/glibc.git/log/?h=gentoo/glibc-2.36-1
[4] https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/azanella/bz23960-dirent
Am Donnerstag, 26. Januar 2023, 00:57:31 CET schrieb Andreas K. Huettel:
> Dear all,
>
> now that the 2.37 release and with that another half year of delay is near,
> I'd like to remind everyone that we still need to find some decent solution
> for the remaining problems associated with time64 and LFS as discussed
> earlier [1].
>
> As far as I can see at the moment there are two things that need a solution.
>
> 1) qemu usermode emulation is broken when emulating a 32bit arch from a 64bit
> arch, bug 23960
>
> 2) the transition to default time64 breaks legacy 32bit binaries in
> unpredictable ways
>
> I'm going to reply with two separate e-mails for these issues, and would be
> very happy for your opinions and contributions on the respective threads.
>
> Cheers,
> Andreas
> (Gentoo toolchain team)
>
> [1] https://sourceware.org/pipermail/libc-alpha/2022-November/143386.html
>
>
--
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2023-01-25 23:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-25 23:57 The time64 and Large File Support mess Andreas K. Huettel
2023-01-25 23:58 ` Andreas K. Huettel [this message]
2023-01-26 12:21 ` time64 / Large File Support: 1) [2.28 Regression]: New getdents{64} implementation breaks qemu-user Adhemerval Zanella Netto
2023-01-27 20:08 ` Andreas K. Huettel
2023-01-25 23:59 ` time64 / Large File Support: 2) default time64 breaks legacy 32bit binaries Andreas K. Huettel
2023-01-26 4:13 ` Paul Eggert
2023-01-26 13:21 ` Adhemerval Zanella Netto
2023-01-26 23:35 ` Sam James
2023-01-27 17:33 ` Adhemerval Zanella Netto
2023-02-01 16:26 ` Florian Weimer
2023-02-01 19:47 ` Sam James
2023-02-01 19:54 ` Sam James
2023-02-03 17:52 ` Florian Weimer
2023-02-01 22:22 ` Michael Hudson-Doyle
2023-02-03 14:17 ` Adhemerval Zanella Netto
2023-02-03 18:56 ` Florian Weimer
2023-01-27 2:38 ` Paul Eggert
2023-01-27 17:40 ` Adhemerval Zanella Netto
2023-01-27 23:51 ` Paul Eggert
2023-01-27 23:58 ` Joseph Myers
2023-02-01 12:27 ` Adhemerval Zanella Netto
2023-01-26 10:43 ` Florian Weimer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6847475.SvYEEZNnvj@pinacolada \
--to=dilfridge@gentoo.org \
--cc=libc-alpha@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).