From: Liu Bo <bo.li.liu@oracle.com>
To: Jan Schmidt <list.btrfs@jan-o-sch.net>
Cc: Josef Bacik <jbacik@fusionio.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3] Btrfs: fix crash regarding to ulist_add_merge
Date: Mon, 29 Jul 2013 21:11:43 +0800 [thread overview]
Message-ID: <20130729131036.GA29613@localhost.localdomain> (raw)
In-Reply-To: <51F62686.7090800@jan-o-sch.net>
On Mon, Jul 29, 2013 at 10:23:34AM +0200, Jan Schmidt wrote:
> On Fri, June 28, 2013 at 06:37 (+0200), Liu Bo wrote:
> > Several users reported this crash of NULL pointer or general protection,
> > the story is that we add a rbtree for speedup ulist iteration, and we
> > use krealloc() to address ulist growth, and krealloc() use memcpy to copy
> > old data to new memory area, so it's OK for an array as it doesn't use
> > pointers while it's not OK for a rbtree as it uses pointers.
> >
> > So krealloc() will mess up our rbtree and it ends up with crash.
> >
> > Reviewed-by: Wang Shilong <wangsl-fnst@cn.fujitsu.com>
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > v3: fix a return value problem(Thanks Wang Shilong).
> > v2: fix an use-after-free bug and a finger error(Thanks Zach and Josef).
> >
> > fs/btrfs/ulist.c | 15 +++++++++++++++
> > 1 files changed, 15 insertions(+), 0 deletions(-)
> >
> > diff --git a/fs/btrfs/ulist.c b/fs/btrfs/ulist.c
> > index 7b417e2..b0a523b2 100644
> > --- a/fs/btrfs/ulist.c
> > +++ b/fs/btrfs/ulist.c
> > @@ -205,6 +205,10 @@ int ulist_add_merge(struct ulist *ulist, u64 val, u64 aux,
> > u64 new_alloced = ulist->nodes_alloced + 128;
> > struct ulist_node *new_nodes;
> > void *old = NULL;
> > + int i;
> > +
> > + for (i = 0; i < ulist->nnodes; i++)
> > + rb_erase(&ulist->nodes[i].rb_node, &ulist->root);
> >
> > /*
> > * if nodes_alloced == ULIST_SIZE no memory has been allocated
> > @@ -224,6 +228,17 @@ int ulist_add_merge(struct ulist *ulist, u64 val, u64 aux,
> >
> > ulist->nodes = new_nodes;
> > ulist->nodes_alloced = new_alloced;
> > +
> > + /*
> > + * krealloc actually uses memcpy, which does not copy rb_node
> > + * pointers, so we have to do it ourselves. Otherwise we may
> > + * be bitten by crashes.
> > + */
> > + for (i = 0; i < ulist->nnodes; i++) {
> > + ret = ulist_rbtree_insert(ulist, &ulist->nodes[i]);
> > + if (ret < 0)
> > + return ret;
> > + }
> > }
> > ulist->nodes[ulist->nnodes].val = val;
> > ulist->nodes[ulist->nnodes].aux = aux;
> >
>
> Reviewed-by: Jan Schmidt <list.btrfs@jan-o-sch.net>
>
> Josef, how about sending this one for the next 3.11 rc and to 3.10 stable? Any
> objections?
A good candidate for -stable, along with josef's 'last ref' fixes about
__tree_mod_log_rewind(), thanks,
-liubo
prev parent reply other threads:[~2013-07-29 13:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 4:37 [PATCH v3] Btrfs: fix crash regarding to ulist_add_merge Liu Bo
2013-06-28 19:43 ` Zach Brown
2013-06-29 10:46 ` Liu Bo
2013-07-29 8:23 ` Jan Schmidt
2013-07-29 13:11 ` Liu Bo [this message]
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=20130729131036.GA29613@localhost.localdomain \
--to=bo.li.liu@oracle.com \
--cc=jbacik@fusionio.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=list.btrfs@jan-o-sch.net \
/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).