public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "adhemerval.zanella at linaro dot org" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31186] Some dirent/io tests don't work on xfs
Date: Fri, 29 Dec 2023 19:42:34 +0000	[thread overview]
Message-ID: <bug-31186-131-dC0DnsWlGy@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31186-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=31186

--- Comment #6 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Adhemerval Zanella from comment #5)
> Right, so XFS essentially does not support non-LFS calls. I am not sure
> which is the best way to handle it, with my patchset I can also clamp d_ino
> and not advertise EOVERFLOW.  I am not fully sure about the implications.

Scratch that, I just recalled that we always use getdents64 syscall even for
non-LFS.  As fair I recall, EXT4 will clamp the values anyway so I think glibc
will either need to do something similar or revert to use non-LFS getdents
syscall (which I would like to avoid...).

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-12-29 19:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-22 16:18 [Bug libc/31186] New: " hjl.tools at gmail dot com
2023-12-29 13:29 ` [Bug libc/31186] " adhemerval.zanella at linaro dot org
2023-12-29 15:49 ` hjl.tools at gmail dot com
2023-12-29 18:32 ` adhemerval.zanella at linaro dot org
2023-12-29 18:56 ` hjl.tools at gmail dot com
2023-12-29 19:25 ` adhemerval.zanella at linaro dot org
2023-12-29 19:42 ` adhemerval.zanella at linaro dot org [this message]
2023-12-29 20:00 ` adhemerval.zanella at linaro dot org
2023-12-29 21:53 ` hjl.tools at gmail dot com
2023-12-29 23:52 ` sam at gentoo dot org
2023-12-30 12:29 ` fw at deneb dot enyo.de
2024-01-02 18:06 ` adhemerval.zanella at linaro 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-31186-131-dC0DnsWlGy@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).