From: "Ludovic Courtès" <ludo@gnu.org>
To: 58803@debbugs.gnu.org
Subject: bug#58803: coreutils-8.32 test failure on i586-gnu
Date: Wed, 26 Oct 2022 19:20:07 +0200 [thread overview]
Message-ID: <87r0yu1ozc.fsf@inria.fr> (raw)
Native builds of coreutils-8.32 (ca. commit
3734857fc55df2c599c2fe5cc4ae49f5d47879fc) have one test failure on
i586-gnu:
--8<---------------cut here---------------start------------->8---
+ skip_if_root_
+ uid_is_privileged_
++ id -u
+ my_uid=999
+ case $my_uid in
+ return 1
+ touch unreadable
+ chmod a-r unreadable
+ df unreadable
df: Warning: cannot read table of mounted file systems: No such file or directory
Filesystem 1K-blocks Used Available Use% Mounted on
- 12288000 2916208 8757392 25% /
+ mkfifo_or_skip_ fifo
+ test 1 = 1
+ mkfifo fifo
+ timeout 10 df fifo
df: Warning: cannot read table of mounted file systems: No such file or directory
+ fail=1
+ test 1 = 1
+ dump_mount_list_
+ cat /proc/self/mountinfo
cat: /proc/self/mountinfo: No such file or directory
+ cat /proc/self/mounts
cat: /proc/self/mounts: No such file or directory
+ cat /proc/mounts
/dev/hd0s1 / ext2fs writable,store-type=typed 0 0
proc /proc /hurd/procfs defaults 0 0
none /dev/shm /hurd/tmpfs writable,no-sync,size=1514772K 0 0
+ Exit 1
+ set +e
+ exit 1
+ exit 1
+ remove_tmp_
+ __st=1
+ cleanup_
+ :
+ test '' = yes
+ cd /tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32
+ chmod -R u+rwx /tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/gt-unreadable.sh.6E92
+ rm -rf /tmp/guix-build-coreutils-8.32.drv-0/coreutils-8.32/gt-unreadable.sh.6E92
+ exit 1
FAIL tests/df/unreadable.sh (exit status: 1)
--8<---------------cut here---------------end--------------->8---
Indeed, ‘df’ seems to read FIFOs as if they were regular files:
--8<---------------cut here---------------start------------->8---
ludo@childhurd ~$ mkfifo fifo
ludo@childhurd ~$ ls -l fifo
prw-r--r-- 1 ludo users 0 Oct 21 07:08 fifo
ludo@childhurd ~$ df ./fifo
df: Warning: cannot read table of mounted file systems: No such file or directory
^C
--8<---------------cut here---------------end--------------->8---
It would seem that it’s stuck on a ‘dir_lookup’ RPC:
--8<---------------cut here---------------start------------->8---
135<--132(pid83)->io_identity_request () = 0 137<--136(pid83) 131<--133(pid83) 29419
task109(pid83)-> 3206 (pn{ 18}) = 0
task109(pid83)-> 3206 (pn{ 19}) = 0
task109(pid83)-> 3206 (pn{ 17}) = 0
task109(pid83)-> 3206 (pn{ 19}) = 0
task109(pid83)-> 3206 (pn{ 17}) = 0
task109(pid83)-> 3206 (pn{ 16}) = 0
task109(pid83)-> 3206 (pn{ 14}) = 0
task109(pid83)-> 3206 (pn{ 17}) = 0
task109(pid83)-> 3206 (pn{ 14}) = 0
task109(pid83)-> 2023 (17022976 4096) = 0
86<--120(pid83)->dir_lookup ("home/ludo/fifo" 65 0) ...113
task109(pid83)-> 2021 (0 4096 1) = 0 17018880
task109(pid83)-> 3208 (pn{ 13} 0 1) = 0
task109(pid83)-> 3206 (pn{ 13}) = 0
--8<---------------cut here---------------end--------------->8---
… where 65 = O_NOTRANS | O_RDONLY.
Passing O_NOTRANS (without O_RDONLY) like the ‘stat’ command does works
fine.
Maybe /hurd/fifo needs to implement ‘trivfs_check_open_hook’ to avoid
actually opening?
Ludo’.
next reply other threads:[~2022-10-26 17:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 17:20 Ludovic Courtès [this message]
2022-11-26 11:53 ` bug#58803: coreutils-8.32 test failure on i586-gnu Samuel Thibault
2022-11-26 15:35 ` Ludovic Courtès
2023-07-18 20:09 ` Ludovic Courtès
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=87r0yu1ozc.fsf@inria.fr \
--to=ludo@gnu.org \
--cc=58803@debbugs.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).