From: Nick Piggin <npiggin@suse.de>
To: Jens Axboe <jens.axboe@oracle.com>
Cc: "Yan, Zheng " <yanzheng@21cn.com>,
Chris Mason <chris.mason@oracle.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [patch] btrfs: fix inode rbtree corruption
Date: Wed, 19 Aug 2009 10:45:30 +0200 [thread overview]
Message-ID: <20090819084530.GD25721@wotan.suse.de> (raw)
In-Reply-To: <20090818211910.GR12579@kernel.dk>
On Tue, Aug 18, 2009 at 11:19:10PM +0200, Jens Axboe wrote:
> On Wed, Aug 19 2009, Yan, Zheng wrote:
> > 2009/8/19 Nick Piggin <npiggin@suse.de>:
> > > Hi,
> > >
> > > Ran into a problem stress testing my btrfs truncate conversion attempt...
> > > Unfortunately it was an existing btrfs problem. Fortunately I think I
> > > was able to fix it.
> > >
> > > Thanks,
> > > Nick
> > >
> > > --
> > > btrfs: fix inode rbtree corruption
> > >
> > > Node may not be inserted over existing node. This causes inode tree
> > > corruption and I was seeing crashes in inode_tree_del which I can not
> > > reproduce after this patch.
> > >
> > > The other way to fix this would be to tie inode lifetime in the rbtree
> > > with inode while not in freeing state. I had a look at this but it is
> > > not so trivial at this point. At least this patch gets things working again.
> > >
> >
> > I'm not quite understand this. rbtree allows entries having the same keys.
> > I guess your problem is because of some nodes get inserted into the tree
> > twice. But I have no idea how can it happen.
>
> It can work with key aliases, if it's a problem then it's likely due to
> another problem in related lookup code.
See my other reply. It *can* work with key aliases, but this particular
code does not.
It is pretty easy obviously to put in duplicates because the rbtree
code doesn't know about keys, but if we do this then it looks like
it might cause the search code to miss some valid inodes and instead
return freeing inodes -- so you'd also have to look at that and update
it which is why I didn't go down this route..
---
fs/btrfs/inode.c | 13 +++++++------
1 file changed, 7 insertions(+), 6 deletions(-)
Index: linux-2.6/fs/btrfs/inode.c
===================================================================
--- linux-2.6.orig/fs/btrfs/inode.c
+++ linux-2.6/fs/btrfs/inode.c
@@ -3108,13 +3108,14 @@ static void inode_tree_add(struct inode
entry = rb_entry(parent, struct btrfs_inode, rb_node);
if (inode->i_ino < entry->vfs_inode.i_ino)
- p = &(*p)->rb_left;
- else if (inode->i_ino > entry->vfs_inode.i_ino)
- p = &(*p)->rb_right;
+ p = &parent->rb_left;
else {
- WARN_ON(!(entry->vfs_inode.i_state &
- (I_WILL_FREE | I_FREEING | I_CLEAR)));
- break;
+ p = &parent->rb_right;
+ if (inode->i_ino == entry->vfs_inode.i_ino) {
+ /* tolerate duplicates */
+ WARN_ON(!(entry->vfs_inode.i_state &
+ (I_WILL_FREE | I_FREEING | I_CLEAR)));
+ }
}
}
rb_link_node(&BTRFS_I(inode)->rb_node, parent, p);
next prev parent reply other threads:[~2009-08-19 8:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 16:45 [patch] btrfs: fix inode rbtree corruption Nick Piggin
2009-08-18 18:56 ` Yan, Zheng
2009-08-18 21:19 ` Jens Axboe
2009-08-19 8:45 ` Nick Piggin [this message]
2009-08-19 8:46 ` Jens Axboe
2009-08-19 8:52 ` Nick Piggin
2009-08-19 8:59 ` Jens Axboe
2009-08-20 13:23 ` Nick Piggin
2009-08-20 13:51 ` Yan, Zheng
2009-08-20 22:07 ` Jens Axboe
2009-08-21 0:55 ` Yan, Zheng
2009-08-21 6:20 ` Jens Axboe
2009-08-21 8:06 ` Yan, Zheng
2009-08-21 8:10 ` Jens Axboe
2009-08-19 8:56 ` Yan, Zheng
2009-08-19 9:04 ` Nick Piggin
2009-08-19 9:34 ` Yan, Zheng
2009-08-19 10:47 ` Nick Piggin
2009-08-19 12:00 ` Yan, Zheng
2009-08-19 8:32 ` Nick Piggin
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=20090819084530.GD25721@wotan.suse.de \
--to=npiggin@suse.de \
--cc=chris.mason@oracle.com \
--cc=jens.axboe@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=yanzheng@21cn.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