From: Al Viro <viro@ZenIV.linux.org.uk>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [vfs] WARNING: CPU: 0 PID: 3 at fs/dcache.c:255 __d_free()
Date: Mon, 3 Nov 2014 07:17:11 +0000 [thread overview]
Message-ID: <20141103071711.GZ7996@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20141103070142.GB1189@wfg-t540p.sh.intel.com>
On Mon, Nov 03, 2014 at 03:01:42PM +0800, Fengguang Wu wrote:
> Hi Al,
>
> 0day kernel testing robot got the below dmesg and the first bad commit is
>
> git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git for-next
>
> commit ff1995cbc0eb7c4beeca313a150111e3e3622e2c
> Author: Al Viro <viro@zeniv.linux.org.uk>
> AuthorDate: Sun Oct 26 19:19:16 2014 -0400
> Commit: Al Viro <viro@zeniv.linux.org.uk>
> CommitDate: Fri Oct 31 13:04:16 2014 -0400
>
Right, but the warning is a false positive - both of these WARN_ON should
be moved to dentry_free() (both the __d_free() and __d_free_external() ones,
that is). Will fix and push tomorrow morning...
parent reply other threads:[~2014-11-03 7:17 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20141103070142.GB1189@wfg-t540p.sh.intel.com>]
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=20141103071711.GZ7996@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=fengguang.wu@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
/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).