From: Chris Mason <clm@fb.com>
To: Pedro Fonseca <pfonseca@mpi-sws.org>, <linux-btrfs@vger.kernel.org>
Subject: Re: Warning in inode_tree_add() -- !(entry->vfs_inode.i_state & (I_WILL_FREE | I_FREEING)
Date: Tue, 10 Dec 2013 08:25:29 -0500 [thread overview]
Message-ID: <20131210132529.16869.59608@ret> (raw)
In-Reply-To: <52A63302.4020301@mpi-sws.org>
Quoting Pedro Fonseca (2013-12-09 16:15:46)
> Hi,
>
> I've got multiple instances of warnings caused by the statement
> "WARN_ON(!(entry->vfs_inode.i_state & (I_WILL_FREE | I_FREEING)));" in
> inode_tree_add(). The tests were executed on the official 3.12.2 kernel.
> Do you think it's something serious?
Definitely. You're in the autodefrag code here and an iget is replacing
an existing inode that wasn't ready to be replaced. What test are you
running?
-chris
next prev parent reply other threads:[~2013-12-10 13:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 21:15 Warning in inode_tree_add() -- !(entry->vfs_inode.i_state & (I_WILL_FREE | I_FREEING) Pedro Fonseca
2013-12-10 13:25 ` Chris Mason [this message]
2013-12-10 15:53 ` Pedro Fonseca
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=20131210132529.16869.59608@ret \
--to=clm@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=pfonseca@mpi-sws.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).