From: "J. Bruce Fields" <bfields@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Josef Bacik <jbacik@fb.com>,
kernel test robot <xiaolong.ye@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>, Chris Mason <clm@fb.com>,
David Sterba <dsterba@suse.com>,
LKML <linux-kernel@vger.kernel.org>, LKP <lkp@01.org>,
linux-btrfs <linux-btrfs@vger.kernel.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} still in use (1) [unmount of btrfs vda]
Date: Wed, 10 Aug 2016 15:09:16 -0400 [thread overview]
Message-ID: <20160810190915.GA22411@pad> (raw)
In-Reply-To: <CA+55aFw5DczMkEYP47h=-9f6U2V5aQUhSxqPjtTbNp1Dd=gZwQ@mail.gmail.com>
On Wed, Aug 10, 2016 at 11:56:15AM -0700, Linus Torvalds wrote:
> On Wed, Aug 10, 2016 at 11:46 AM, Josef Bacik <jbacik@fb.com> wrote:
> >
> > So my naive fix would be something like this
>
> Bruce? Josef's patch looks ObviouslyCorrect(tm) to me now that I look
> at it - all the other callers of fh_compose() also seem to just drop
> the dentry unconditionally, knowing that fh_compose() took a ref to it
> if needed.
>
> In fact, the only thing I'd do differently would be to not even put
> the comment there at all, since this call site isn't any different
> from any of the others. If anything, it could go on fh_compose() if we
> want to add comments.
Yep, makes sense to me too.
OK with me if you want to take it, otherwise I'll run it through my
usual tests and send you a pull request probably today or tomorrow.
Thanks, Josef! (And kernel test robot folks--the speed with which
they're catching stuff, and bisecting down to individual commits, is
really amazing to me.)
--b.
next prev parent reply other threads:[~2016-08-10 19:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-10 5:39 [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} still in use (1) [unmount of btrfs vda] kernel test robot
2016-08-10 18:06 ` Linus Torvalds
2016-08-10 18:22 ` Josef Bacik
2016-08-10 18:25 ` Linus Torvalds
2016-08-10 18:32 ` Josef Bacik
2016-08-10 18:46 ` Josef Bacik
2016-08-10 18:56 ` Linus Torvalds
2016-08-10 19:09 ` J. Bruce Fields [this message]
2016-08-10 19:15 ` Linus Torvalds
2016-08-10 19:06 ` Jeff Layton
2016-08-11 2:19 ` 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=20160810190915.GA22411@pad \
--to=bfields@redhat.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=lkp@01.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
--cc=xiaolong.ye@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox