From: Dave Chiluk <chiluk@canonical.com>
To: Petr Vandrovec <petr@vandrovec.name>
Cc: linux-kernel@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [PATCH] ncpfs: fix rmdir returns Device or resource busy
Date: Wed, 05 Jun 2013 15:20:07 -0500 [thread overview]
Message-ID: <51AF9D77.2000901@canonical.com> (raw)
In-Reply-To: <CA+i2_De5HHw2H9SvZ=W+QAOcy0M7jFac88OK6aeYdJVCGL6b+A@mail.gmail.com>
Petr do you still have commit rights to ncpfs? Can you please commit it
to upstream or do I have to get Al to do that?
Dave.
On 05/31/2013 05:22 PM, Petr Vandrovec wrote:
> Looks OK to me.
>
> As I said elsewhere, I do not use ncpfs for years so I cannot provide
> any sensible maintainership for it anymore :-(
>
> Petr
>
> On May 31, 2013 2:40 PM, "Dave Chiluk" <chiluk@canonical.com
> <mailto:chiluk@canonical.com>> wrote:
>
> Any thoughts on this? NCPFS seems to be the forgotten, left-behind,
> red-headed stepchild of the fs community.
>
> Dave.
>
> On 05/28/2013 05:50 PM, Dave Chiluk wrote:
> > 1d2ef5901483004d74947bbf78d5146c24038fe7 caused a regression in
> ncpfs such that
> > directories could no longer be removed. This was because
> ncp_rmdir checked
> > to see if a dentry could be unhashed before allowing it to be
> removed. Since
> > 1d2ef5901483004d74947bbf78d5146c24038fe7 introduced a change that
> incremented
> > dentry->d_count causing it to always be greater than 1 unhash
> would always
> > fail. Thus causing the error path in ncp_rmdir to always be
> taken. Removing
> > this error path is safe as unhashing is still accomplished by
> calls to dput
> > from vfs_rmdir.
> > ---
> > fs/ncpfs/dir.c | 9 ---------
> > 1 file changed, 9 deletions(-)
> >
> > diff --git a/fs/ncpfs/dir.c b/fs/ncpfs/dir.c
> > index 8163260..6792ce1 100644
> > --- a/fs/ncpfs/dir.c
> > +++ b/fs/ncpfs/dir.c
> > @@ -1029,15 +1029,6 @@ static int ncp_rmdir(struct inode *dir,
> struct dentry *dentry)
> > DPRINTK("ncp_rmdir: removing %s/%s\n",
> > dentry->d_parent->d_name.name <http://d_name.name>,
> dentry->d_name.name <http://d_name.name>);
> >
> > - /*
> > - * fail with EBUSY if there are still references to this
> > - * directory.
> > - */
> > - dentry_unhash(dentry);
> > - error = -EBUSY;
> > - if (!d_unhashed(dentry))
> > - goto out;
> > -
> > len = sizeof(__name);
> > error = ncp_io2vol(server, __name, &len, dentry->d_name.name
> <http://d_name.name>,
> > dentry->d_name.len, !ncp_preserve_case(dir));
> >
>
next prev parent reply other threads:[~2013-06-05 20:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-28 22:50 [PATCH] ncpfs: fix rmdir returns Device or resource busy Dave Chiluk
2013-05-31 21:40 ` Dave Chiluk
[not found] ` <CA+i2_De5HHw2H9SvZ=W+QAOcy0M7jFac88OK6aeYdJVCGL6b+A@mail.gmail.com>
2013-06-05 20:20 ` Dave Chiluk [this message]
2013-06-07 6:43 ` Petr Vandrovec
2013-06-07 16:09 ` Dave Chiluk
2013-06-07 16:14 ` Al Viro
2013-06-13 2:01 ` Al Viro
2013-06-13 6:42 ` Al Viro
2013-06-14 4:19 ` Dave Chiluk
2013-06-15 5:09 ` Al Viro
2013-06-15 5:26 ` Al Viro
2013-06-14 4:02 ` Dave Chiluk
2013-06-19 9:30 ` Luis Henriques
2013-06-26 1:05 ` Ben Hutchings
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=51AF9D77.2000901@canonical.com \
--to=chiluk@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=petr@vandrovec.name \
--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