From: samba-bugs@samba.org
To: cifs-qa@samba.org
Subject: [Bug 15123] getxattr() on cifs sometimes hangs since kernel 5.14
Date: Fri, 15 Jul 2022 21:23:35 +0000 [thread overview]
Message-ID: <bug-15123-10630-zpEHmlqsiC@https.bugzilla.samba.org/> (raw)
In-Reply-To: <bug-15123-10630@https.bugzilla.samba.org/>
https://bugzilla.samba.org/show_bug.cgi?id=15123
--- Comment #1 from Forest <forestix@sonic.net> ---
I can reliably reproduce it booting from this live USB image:
kubuntu-22.04-desktop-amd64.iso
My setup steps when using that live USB environment:
sudo mount.cifs //myserver/dir ~/mnt/dir -o username=myuser,uid=999,gid=999
touch ~/mnt/dir/test{1..5}
Tests and results:
(My reproducer program is called xattrtest in these command lines.)
# 1 thread is fast
# (note the system call duration reported by strace in <> brackets)
$ time ./xattrtest ~/mnt/dir/test{1..5}
real 0m0.079s
user 0m0.003s
sys 0m0.000s
$ strace -Te getxattr ./xattrtest ~/mnt/dir/test1
getxattr("/home/myuser/mnt/dir/test1", "user.baloo.rating", NULL, 0) = -1
ENODATA (No data available) <0.008482>
# 2+ threads are slow
$ time ./xattrtest -t 2 ~/mnt/dir/test{1..5}
real 0m5.118s
user 0m0.005s
sys 0m0.000s
$ strace -Te getxattr ./xattrtest -t 2 ~/mnt/dir/test1
getxattr("/home/myuser/mnt/dir/test1", "user.baloo.rating", NULL, 0) = -1
ENODATA (No data available) <1.018507>
# 2+ threads are fast if I remount with the nouser_xattr option
$ time ./xattrtest -t 2 ~/mnt/dir/test{1..5}
real 0m0.061s
user 0m0.002s
sys 0m0.000s
$ strace -Te getxattr ./xattrtest -t 2 ~/mnt/dir/test1
getxattr("/home/myuser/mnt/dir/test1", "user.baloo.rating", NULL, 0) = -1
EOPNOTSUPP (Operation not supported) <0.000048>
--
You are receiving this mail because:
You are the QA Contact for the bug.
prev parent reply other threads:[~2022-07-15 21:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 21:17 [Bug 15123] New: getxattr() on cifs sometimes hangs since kernel 5.14 samba-bugs
2022-07-15 21:23 ` samba-bugs [this message]
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-15123-10630-zpEHmlqsiC@https.bugzilla.samba.org/ \
--to=samba-bugs@samba.org \
--cc=cifs-qa@samba.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