From: "Andreas K. Huettel" <mail@akhuettel.de>
To: libc-alpha@sourceware.org
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Subject: Re: [PATCH v5 0/5] Fix opendir regression on some FS
Date: Thu, 09 Feb 2023 21:14:22 +0100 [thread overview]
Message-ID: <1915877.6tgchFWduM@pinacolada> (raw)
In-Reply-To: <20230127172834.391311-1-adhemerval.zanella@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Am Freitag, 27. Januar 2023, 18:28:29 CET schrieben Sie:
> Some filesystem might return a non-representable d_off on getdents
> call, even if there are few entries in the directories (for instance
> ext4, which returns a hash). This trigger issues with non-LFS readdir
[...]
Ping- anything still missing here? Thanks :)
--
Andreas K. Huettel
tel. +49 151 241 67748 (mobile)
e-mail mail@akhuettel.de
http://www.akhuettel.de/private/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]
next prev parent reply other threads:[~2023-02-09 20:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 17:28 Adhemerval Zanella
2023-01-27 17:28 ` [PATCH v5 1/5] linux: Use getdents64 on non-LFS readdir Adhemerval Zanella
2023-01-27 17:38 ` Andreas Schwab
2023-02-20 13:31 ` Florian Weimer
2023-02-20 17:55 ` Florian Weimer
2023-03-01 16:34 ` Adhemerval Zanella Netto
2023-01-27 17:28 ` [PATCH v5 2/5] linux: Set internal DIR filepos as off64_t (BZ #23960, BZ #24050) Adhemerval Zanella
2023-02-20 18:39 ` Florian Weimer
2023-03-01 17:40 ` Adhemerval Zanella Netto
2023-01-27 17:28 ` [PATCH v5 3/5] linux: Add __readdir64_unlocked Adhemerval Zanella
2023-01-27 17:28 ` [PATCH v5 4/5] linux: Add __old_readdir64_unlocked Adhemerval Zanella
2023-01-27 17:28 ` [PATCH v5 5/5] linux: Use getdents64 on readdir64 compat implementation Adhemerval Zanella
2023-02-09 20:14 ` Andreas K. Huettel [this message]
2023-02-09 20:14 ` [PATCH v5 0/5] Fix opendir regression on some FS Andreas K. Huettel
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=1915877.6tgchFWduM@pinacolada \
--to=mail@akhuettel.de \
--cc=adhemerval.zanella@linaro.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).