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: Tue, 02 Jan 2024 18:06:37 +0000 [thread overview]
Message-ID: <bug-31186-131-a5SYOKXMYx@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31186-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31186
Adhemerval Zanella <adhemerval.zanella at linaro dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Ever confirmed|1 |0
Status|NEW |UNCONFIRMED
--- Comment #10 from Adhemerval Zanella <adhemerval.zanella at linaro dot org> ---
(In reply to Florian Weimer from comment #9)
> 32-bit compatibility on XFS requires using the inode32 option:
> https://www.man7.org/linux/man-pages/man5/xfs.5.html
>
> (No such option exists with btrfs, by the way, and you need to reformat if
> you exceed the 32-bit inode space.)
>
> So I think this bug is different from the d_off issue and invalid from a
> glibc perspective.
The dirent/list failure is related, since on my BZ#28824 proposed fix I did not
consider that d_ino might overflow. But the rest of the failures do seem to be
related to the XFS inode64, where symlink (io/tst-ftw-lnk) and stat
(io/ftwtest) are failing due FS overflow values.
Should we mark this as WONTFIX/NOTABUG?
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2024-01-02 18:06 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
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 [this message]
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-a5SYOKXMYx@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).