From: Jens Axboe <jens.axboe@oracle.com>
To: "Yan, Zheng " <yanzheng@21cn.com>
Cc: Nick Piggin <npiggin@suse.de>,
Chris Mason <chris.mason@oracle.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [patch] btrfs: fix inode rbtree corruption
Date: Fri, 21 Aug 2009 00:07:36 +0200 [thread overview]
Message-ID: <20090820220736.GQ12579@kernel.dk> (raw)
In-Reply-To: <3d0408630908200651i4bfbf0ebk6b18975e1a06da7e@mail.gmail.com>
On Thu, Aug 20 2009, Yan, Zheng wrote:
> 2009/8/20 Nick Piggin <npiggin@suse.de>:
> > On Wed, Aug 19, 2009 at 10:59:07AM +0200, Jens Axboe wrote:
> >> On Wed, Aug 19 2009, Nick Piggin wrote:
> >> > On Wed, Aug 19, 2009 at 10:46:59AM +0200, Jens Axboe wrote:
> >> > > On Wed, Aug 19 2009, Nick Piggin wrote:
> >> > > > 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..
> >> > >
> >> > > Mine was just a generic statement, I didn't read the btrfs code (hence
> >> > > my comment about potential lookup bug, if you allow aliases you have to
> >> > > be careful).
> >> >
> >> > Ah ok. Well yeah in this case btrfs is definitely wrong in the way it
> >> > tried to insert aliases.
> >>
> >> I looked at the actual problem now and I agree, it cannot work that way.
> >> I don't know if Linus is planning another -rc, we should probably get
> >> this upstream sooner rather than later. Chris is away this week, so if
> >> we can get Yan to agree on this patch as well, I'll submit it.
> > I think the first patch I submitted was agreed?
> >
>
> Of course, thank you.
Yan, are you sending this upstream?
--
Jens Axboe
next prev parent reply other threads:[~2009-08-20 22:07 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
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 [this message]
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=20090820220736.GQ12579@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=chris.mason@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=npiggin@suse.de \
--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