From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ext4@vger.kernel.org
Subject: [Bug 205957] Ext4 64 bit hash breaks 32 bit glibc 2.28+
Date: Wed, 25 Dec 2019 22:53:13 +0000 [thread overview]
Message-ID: <bug-205957-13602-9v8DcYwBox@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205957-13602@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205957
--- Comment #9 from aladjev.andrew@gmail.com (aladjev.andrew@gmail.com) ---
I've created heavy (but easy) bunch of patches that fixes issue. This is the
order of right patches applyment (for gentoo):
+----------------------------------------------------------------------------+
| |
| amd64 host: +-------------------------------------------------+ |
| | | |
| linux-headers: kernel | amd64 container: +-----------------------+ | |
| gentoo-sources: kernel | | | | |
| libseccomp | linux-headers: kernel | arm container (qemu): | | |
| go | qemu | | | |
| buildah | | linux-headers: kernel | | |
| | | glibc | | |
| | | | | |
| | +-----------------------+ | |
| | | |
| +-------------------------------------------------+ |
| |
+----------------------------------------------------------------------------+
You can find full example here
https://github.com/andrew-aladev/test-images/tree/master/cross/arm-unknown-linux-gnueabi.
Now I am able to emerge several application inside arm container (qemu), so
glibc with "getdents64_x32" works perfect.
I understand that kernel developers don't like additional syscalls, so they
won't accept such kernel patch. But this syscall is the easiest way for me to
provide a proof of concept.
How to understand these patches? Please read "glibc.patch". Our amd64 kernel is
the common kernel for amd64, i386 and arm (via qemu). amd64 is using
"getdents64" and arm (without LFS) is using "getdents64_x32". We need to have 2
syscalls simultaneously: "getdents64" and "getdents64_x32" or maybe single
syscall with some "x32" flag. I think this will be the most reliable solution.
I want to ask glibc and kernel developers to cooperate and find the right
solution. This is important not only for arm, it looks like this issue affects
any x32 abi.
Thank you.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2019-12-25 22:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-24 14:07 [Bug 205957] New: Ext4 64 bit hash breaks 32 bit glibc 2.28+ bugzilla-daemon
2019-12-24 14:07 ` [Bug 205957] " bugzilla-daemon
2019-12-24 15:09 ` bugzilla-daemon
2019-12-24 18:16 ` bugzilla-daemon
2019-12-25 22:50 ` bugzilla-daemon
2019-12-25 22:51 ` bugzilla-daemon
2019-12-25 22:51 ` bugzilla-daemon
2019-12-25 22:52 ` bugzilla-daemon
2019-12-25 22:52 ` bugzilla-daemon
2019-12-25 22:52 ` bugzilla-daemon
2019-12-25 22:53 ` bugzilla-daemon [this message]
2019-12-28 7:50 ` bugzilla-daemon
2019-12-28 9:00 ` bugzilla-daemon
2019-12-28 11:20 ` bugzilla-daemon
2020-01-05 21:47 ` bugzilla-daemon
2020-01-05 22:08 ` bugzilla-daemon
2020-01-08 23:11 ` bugzilla-daemon
2020-01-09 20:02 ` bugzilla-daemon
2020-10-02 10:03 ` bugzilla-daemon
2020-10-02 10:34 ` bugzilla-daemon
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=bug-205957-13602-9v8DcYwBox@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-ext4@vger.kernel.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 NNTP newsgroup(s).