From: Michael Leun <lkml20130126@newton.leun.net>
To: linux-kernel@vger.kernel.org
Cc: linux-fsdevel@vger.kernel.org, viro@zeniv.linux.org.uk,
gregkh@linuxfoundation.org
Subject: [REGRESSION] bisected: 3.8 -> 3.9 cannot umount after using fuse
Date: Sat, 4 May 2013 12:45:19 +0200 [thread overview]
Message-ID: <20130504124519.032ac684@xenia.leun.net> (raw)
Mount some filesystem, below that mountpoint as user mount some fuse fs
(tried that with sshfs and fuseiso, both same error), fusermount -u the
fuse fs, try to unmount the filesystem -> busy.
ml@lara:~> id -u
500
ml@lara:~> grep test /etc/fstab
/dev/vg1/test /mnt2 ext4acl,user_xattr,user,noauto 0 0
ml@lara:~> mount /mnt2
ml@lara:~> cd /mnt2
ml@lara:/mnt2> ls -l
insgesamt 24
drwx------ 2 root root 16384 4. Mai 11:24 lost+found
drwxr-xr-x 2 root root 4096 4. Mai 11:44 test
drwxr-xr-x 2 ml users 4096 4. Mai 11:25 xenia
ml@lara:/mnt2> sshfs xenia: xenia
Password:
ml@lara:/mnt2> ls xenia/bla
xenia/bla
ml@lara:/mnt2> fusermount -u xenia
ml@lara:/mnt2> cd
ml@lara:~> umount /mnt2
umount: /mnt2: target is busy.
(In some cases useful info about processes that use
the device is found by lsof(8) or fuser(1))
ml@lara:~> fuser -m /mnt2
ml@lara:~>
It does'nt matter if the mounting and unmounting of the /mnt2
filesystem is done as user or as root, same result.
This works in 3.8(.x). Bisecting yields
57eccb830f1cc93d4b506ba306d8dfa685e0c88f is the first bad commit
commit 57eccb830f1cc93d4b506ba306d8dfa685e0c88f
Author: Al Viro <viro@zeniv.linux.org.uk>
Date: Fri Feb 22 22:49:10 2013 -0500
mount: consolidate permission checks
... and ask for global CAP_SYS_ADMIN only for superblock-level remounts
Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
:040000 040000 4e926c083f6ede645158f02714d73cdd3b233a05 584611744bad96544578259a6fa176577df0ebbd M fs
After reverting 57eccb830f1cc93d4b506ba306d8dfa685e0c88f from 3.9 that
umount above works (not busy).
I've seen that this patch also was identified as problem in relation
with user ns and module loading, see lkml
CAGXu5jLciqXcuhzDVPKPqA+mwv8e28zGAMScatzov3U07BuBaQ@mail.gmail.com
After fixing this upstream the fix should be an stabile candidate.
--
MfG,
Michael Leun
next reply other threads:[~2013-05-04 10:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-04 10:45 Michael Leun [this message]
2013-05-04 15:52 ` [REGRESSION] bisected: 3.8 -> 3.9 cannot umount after using fuse Al Viro
2013-05-04 18:02 ` Michael Leun
2013-05-04 18:43 ` Al Viro
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=20130504124519.032ac684@xenia.leun.net \
--to=lkml20130126@newton.leun.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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 NNTP newsgroup(s).