From: Danny Milosavljevic <dannym@scratchpost.org>
To: Andreas Enge <andreas@enge.fr>
Cc: 43591@debbugs.gnu.org, Marius Bakke <marius@gnu.org>
Subject: [bug#43591] [PATCH core-updates] gnu: glibc-final: Catch all cases of a glibc user not requesting 64-bit offsets and then using readdir.
Date: Sat, 26 Sep 2020 12:50:28 +0200 [thread overview]
Message-ID: <20200926124758.28866f16@scratchpost.org> (raw)
In-Reply-To: <20200925200323.GB5828@jurong>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Hi Andreas,
On Fri, 25 Sep 2020 22:03:23 +0200
Andreas Enge <andreas@enge.fr> wrote:
> On Fri, Sep 25, 2020 at 01:11:18AM +0200, Marius Bakke wrote:
> > Arguably running code for foreign architectures through QEMU binfmt is
> > something of a hack. Mandating that every package *must* be patched to
> > support it seems user-hostile. I'm more in favor of dropping it on the
> > build farm
>
> Indeed it is weird we do not only compile packages natively on the build
> farm.
I'm sorry that my earlier analysis mentioned qemu at all. qemu is not at fault
at all. The same happens if you run 32 bit code on 64 bit hosts without using
qemu! Except for one case: i686 on x86_64--where they have a compatibility
layer in the kernel that works around this problem (which I don't like
either--it obfuscates the problem).
For example a problem appears on:
- armhf on x86_64 host; fault not because of qemu
- armhf on aarch64 host; not using qemu in the first place
And it should appear also on (but I didn't test):
- i686 on aarch64 host; not using qemu in the first place
The problem always appears if the host is 64 bits and the guest is 32 bits,
no matter what cpus both are, except for the case "i686 on x86_64".
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-09-26 10:52 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 14:12 [bug#43591] [PATCH core-updates] gnu: glibc-final: Catch all cases of a glibc user not requesting 64-bit offsets and then using readdir Danny Milosavljevic
2020-09-24 14:16 ` Danny Milosavljevic
2020-09-24 18:17 ` Marius Bakke
2020-09-24 20:27 ` Danny Milosavljevic
2020-09-24 23:11 ` Marius Bakke
2020-09-25 10:20 ` Danny Milosavljevic
2020-09-25 10:42 ` [bug#43591] [PATCH v2 core-updates] gnu: glibc-final: Catch all cases of a glibc user not requesting 64-bit offsets and then using readdir regardless Danny Milosavljevic
2020-09-25 13:36 ` [bug#43591] [PATCH core-updates] gnu: glibc-final: Catch all cases of a glibc user not requesting 64-bit offsets and then using readdir Danny Milosavljevic
2020-09-25 15:33 ` Danny Milosavljevic
2020-09-26 1:42 ` Danny Milosavljevic
2020-09-26 1:49 ` Danny Milosavljevic
2020-09-29 14:51 ` Danny Milosavljevic
2020-09-27 6:43 ` Efraim Flashner
2020-09-25 20:03 ` Andreas Enge
2020-09-26 10:50 ` Danny Milosavljevic [this message]
2020-09-29 20:52 ` Ludovic Courtès
2020-09-29 22:09 ` Danny Milosavljevic
2020-09-30 9:32 ` Ludovic Courtès
2020-09-30 10:28 ` Danny Milosavljevic
2020-10-01 7:14 ` Ludovic Courtès
2020-10-02 7:18 ` Danny Milosavljevic
2020-10-02 8:12 ` Danny Milosavljevic
2020-10-02 9:47 ` Danny Milosavljevic
2020-10-02 9:32 ` Danny Milosavljevic
2020-10-06 15:39 ` Danny Milosavljevic
2020-09-25 10:24 ` Danny Milosavljevic
2020-09-30 8:45 ` [bug#43591] [PATCH core-updates v2 0/5] " Danny Milosavljevic
2020-09-30 8:45 ` [bug#43591] [PATCH core-updates v2 1/5] gnu: glibc-final: Catch all cases of a glibc user not requesting 64-bit offsets and then using readdir regardless Danny Milosavljevic
2020-09-30 16:55 ` Danny Milosavljevic
2020-09-30 8:45 ` [bug#43591] [PATCH core-updates v2 2/5] build-system/gnu: Explicity declare the _FILE_OFFSET_BITS we want Danny Milosavljevic
2020-09-30 8:45 ` [bug#43591] [PATCH core-updates v2 3/5] gnu: glibc: Do not explicitly set _FILE_OFFSET_BITS Danny Milosavljevic
2020-09-30 8:45 ` [bug#43591] [PATCH core-updates v2 4/5] gnu: glibc-mesboot0: " Danny Milosavljevic
2020-09-30 8:45 ` [bug#43591] [PATCH core-updates v2 5/5] gnu: rhash: Explicity declare the _FILE_OFFSET_BITS we want Danny Milosavljevic
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200926124758.28866f16@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=43591@debbugs.gnu.org \
--cc=andreas@enge.fr \
--cc=marius@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).