public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jrtc27 at jrtc27 dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/23960] [2.28 Regression]: New getdents{64} implementation breaks qemu-user
Date: Fri, 02 Oct 2020 13:17:15 +0000 [thread overview]
Message-ID: <bug-23960-131-Y2z6hoodKV@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23960-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=23960
--- Comment #63 from Jessica Clarke <jrtc27 at jrtc27 dot com> ---
(In reply to Danny Milosavljevic from comment #62)
> (In reply to Florian Weimer from comment #60)
> > (In reply to Danny Milosavljevic from comment #59)
> > > It's impossible to store a 64 bit result into a 32 bit slot.
> >
> > You can do something like that if you can maintain a translation table.
>
> Mathematically speaking, no, you can't. There cannot be a 1:1 mapping
> between all 64 bit values and all 32 bit values.
>
> I know what you mean--in practice it could be good enough, if the directory
> doesn't have too many entries (or, depending on implementation, telldir
> isn't called too often--though first that implementation with only telldir
> doing the counting has to be possible. Is it?).
>
> But that's just kicking the can down the road--eventually, someone somewhere
> will have that many entries. And then, the mapping will fail.
If you have more than 4 billion files then you really should not be using a
32-bit system. That is a very different (if related) problem from a single >4
GiB file. Even https://lwn.net/Articles/400629/ split the 1 billion files up
into 1 thousand directories each with 1 million files.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2020-10-02 13:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-23960-131@http.sourceware.org/bugzilla/>
2019-05-01 20:33 ` chewi at gentoo dot org
2020-09-17 21:42 ` tg at mirbsd dot de
2020-10-02 8:54 ` danny.milo at gmail dot com
2020-10-02 9:36 ` danny.milo at gmail dot com
2020-10-02 9:46 ` fweimer at redhat dot com
2020-10-02 10:41 ` danny.milo at gmail dot com
2020-10-02 11:03 ` danny.milo at gmail dot com
2020-10-02 13:17 ` jrtc27 at jrtc27 dot com [this message]
2020-10-02 14:22 ` adhemerval.zanella at linaro dot org
2020-10-02 23:06 ` tg at mirbsd dot de
2020-10-03 13:54 ` fweimer at redhat dot com
2020-10-03 13:55 ` fweimer at redhat dot com
2021-08-24 11:48 ` glaubitz at physik dot fu-berlin.de
2022-05-15 20:53 ` glaubitz at physik dot fu-berlin.de
2022-05-16 12:06 ` adhemerval.zanella at linaro dot org
2022-05-16 20:11 ` glaubitz at physik dot fu-berlin.de
2022-05-16 20:15 ` adhemerval.zanella at linaro dot org
2022-05-17 4:39 ` sam at gentoo dot org
2022-12-06 15:50 ` glaubitz at physik dot fu-berlin.de
2023-01-13 4:52 ` deller at gmx dot de
2023-12-29 23:52 ` sam at gentoo dot org
2024-01-05 8:33 ` sam at gentoo dot org
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-23960-131-Y2z6hoodKV@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@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).