From: ebiederm@xmission.com (Eric W. Biederman)
To: "Richard W.M. Jones" <rjones@redhat.com>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
Linux-Fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [fuse-devel] fusermount reports "Device or resource busy" but unmounts it anyway
Date: Wed, 13 May 2015 09:50:08 -0500 [thread overview]
Message-ID: <87bnhoilb3.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <20150513082942.GT29283@redhat.com> (Richard W. M. Jones's message of "Wed, 13 May 2015 09:29:42 +0100")
"Richard W.M. Jones" <rjones@redhat.com> writes:
> On Wed, May 13, 2015 at 10:27:09AM +0200, Miklos Szeredi wrote:
>> [CCs added]
>>
>> On Tue, May 12, 2015 at 11:34 AM, Richard W.M. Jones <rjones@redhat.com> wrote:
>> >
>> > Has something changed in FUSE / the kernel in the past few months so
>> > that 'fusermount -u /mp' reports the error:
>> >
>> > fusermount: failed to unmount /mp: Device or resource busy
>> >
>>
>> That's from the umount2() syscall, and most likely not a fuse issue.
>>
>> > and returns a non-zero exit code, but the mountpoint is unmounted
>> > anyway?
>>
>> Is this in 4.1-rc? If so, then the recent fs/namespace.c patches from
>> Eric Biederman would be suspect.
>
> Yes, this is reproducible with:
>
> kernel-4.1.0-0.rc2.git3.1.fc23.x86_64 (from Fedora Rawide)
> fuse-2.9.3-4.fc22.x86_64
>
> I will see if I can make a small reproducer and get back.
I will be happy to look at this if there is a reasonably small reproducer.
I don't think I changed anything that could cause that kind of failure,
but I have touched a fair amount of that code recently and at the very
least I will be familiar with it.
The only case I can imagine is the mount point being deleted.
Eric
prev parent reply other threads:[~2015-05-13 14:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150512093413.GA19964@redhat.com>
2015-05-13 8:27 ` [fuse-devel] fusermount reports "Device or resource busy" but unmounts it anyway Miklos Szeredi
2015-05-13 8:29 ` Richard W.M. Jones
2015-05-13 14:50 ` Eric W. Biederman [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=87bnhoilb3.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=rjones@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.