All of lore.kernel.org
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: kernel test robot <xiaolong.ye@intel.com>,
	Al Viro <viro@zeniv.linux.org.uk>, Chris Mason <clm@fb.com>,
	Josef Bacik <jbacik@fb.com>, David Sterba <dsterba@suse.com>
Cc: "J. Bruce Fields" <bfields@redhat.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 11:06:35 -0700	[thread overview]
Message-ID: <CA+55aFxdcG4y4zWTFFT8SekEtxsvx12P+e=11kTCFc=zS__bXQ@mail.gmail.com> (raw)
In-Reply-To: <20160810053947.GG21941@yexl-desktop>

On Tue, Aug 9, 2016 at 10:39 PM, kernel test robot
<xiaolong.ye@intel.com> wrote:
>
> [ 1537.558739] nfsd: last server has exited, flushing export cache
> [ 1540.627795] BUG: Dentry ffff880027d7c540{i=1846f,n=0a}  still in use (1) [unmount of btrfs vda]
> [ 1540.633915] ------------[ cut here ]------------
> [ 1540.636551] WARNING: CPU: 0 PID: 20552 at fs/dcache.c:1474 umount_check+0x72/0x80

Hmm. Adding Al and the btrfs people to the cc, and expanding the nfs
list. Unlike the flakey-IO warning, this one sounds like a real issue.
Whether it's some dentry leak by nfsd or a VFS or btrfs issue, I can't
begin to guess. Al, ideas?

More information in the original email on lkml.

                 Linus

WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@linux-foundation.org>
To: lkp@lists.01.org
Subject: Re: [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} still in use (1) [unmount of btrfs vda]
Date: Wed, 10 Aug 2016 11:06:35 -0700	[thread overview]
Message-ID: <CA+55aFxdcG4y4zWTFFT8SekEtxsvx12P+e=11kTCFc=zS__bXQ@mail.gmail.com> (raw)
In-Reply-To: <20160810053947.GG21941@yexl-desktop>

[-- Attachment #1: Type: text/plain, Size: 723 bytes --]

On Tue, Aug 9, 2016 at 10:39 PM, kernel test robot
<xiaolong.ye@intel.com> wrote:
>
> [ 1537.558739] nfsd: last server has exited, flushing export cache
> [ 1540.627795] BUG: Dentry ffff880027d7c540{i=1846f,n=0a}  still in use (1) [unmount of btrfs vda]
> [ 1540.633915] ------------[ cut here ]------------
> [ 1540.636551] WARNING: CPU: 0 PID: 20552 at fs/dcache.c:1474 umount_check+0x72/0x80

Hmm. Adding Al and the btrfs people to the cc, and expanding the nfs
list. Unlike the flakey-IO warning, this one sounds like a real issue.
Whether it's some dentry leak by nfsd or a VFS or btrfs issue, I can't
begin to guess. Al, ideas?

More information in the original email on lkml.

                 Linus

  reply	other threads:[~2016-08-10 18:06 UTC|newest]

Thread overview: 22+ 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  5:39 ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " kernel test robot
2016-08-10 18:06 ` Linus Torvalds [this message]
2016-08-10 18:06   ` Linus Torvalds
2016-08-10 18:22   ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Josef Bacik
2016-08-10 18:22     ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " Josef Bacik
2016-08-10 18:25     ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Linus Torvalds
2016-08-10 18:25       ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " Linus Torvalds
2016-08-10 18:32       ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Josef Bacik
2016-08-10 18:32         ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " Josef Bacik
2016-08-10 18:46       ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Josef Bacik
2016-08-10 18:46         ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " Josef Bacik
2016-08-10 18:56         ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Linus Torvalds
2016-08-10 18:56           ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " Linus Torvalds
2016-08-10 19:09           ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " J. Bruce Fields
2016-08-10 19:09             ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " J. Bruce Fields
2016-08-10 19:15             ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Linus Torvalds
2016-08-10 19:15               ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " Linus Torvalds
2016-08-10 19:06         ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Jeff Layton
2016-08-10 19:06           ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " Jeff Layton
2016-08-11  2:19         ` [lkp] [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f,n=0a} " Al Viro
2016-08-11  2:19           ` [nfsd] b44061d0b9: BUG: Dentry ffff880027d7c540{i=1846f, n=0a} " 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='CA+55aFxdcG4y4zWTFFT8SekEtxsvx12P+e=11kTCFc=zS__bXQ@mail.gmail.com' \
    --to=torvalds@linux-foundation.org \
    --cc=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=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 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.