From: Liu Bo <bo.li.liu@oracle.com>
To: Ilya Dryomov <idryomov@gmail.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] Btrfs: fix crash of starting balance
Date: Wed, 16 Jan 2013 09:05:30 +0800 [thread overview]
Message-ID: <20130116010529.GC3942@liubo> (raw)
In-Reply-To: <20130115165903.GB2040@zambezi.lan>
On Tue, Jan 15, 2013 at 06:59:04PM +0200, Ilya Dryomov wrote:
> On Tue, Jan 15, 2013 at 10:47:57PM +0800, Liu Bo wrote:
> > We will crash on BUG_ON(ret == -EEXIST) when we do not resume the existing
> > balance but attempt to start a new one.
> >
> > The steps can be:
> > 1. start balance
> > 2. pause balance
> > 3. start balance
> >
> > Signed-off-by: Liu Bo <bo.li.liu@oracle.com>
> > ---
> > fs/btrfs/volumes.c | 7 ++++++-
> > 1 files changed, 6 insertions(+), 1 deletions(-)
> >
> > diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> > index 5cce6aa..3901654 100644
> > --- a/fs/btrfs/volumes.c
> > +++ b/fs/btrfs/volumes.c
> > @@ -3100,7 +3100,12 @@ int btrfs_balance(struct btrfs_balance_control *bctl,
> > goto out;
> >
> > if (!(bctl->flags & BTRFS_BALANCE_RESUME)) {
> > - BUG_ON(ret == -EEXIST);
> > + /*
> > + * This can happen when we do not resume the existing balance
> > + * but try to start a new one instead.
> > + */
> > + if (ret == -EEXIST)
> > + goto out;
> > set_balance_control(bctl);
> > } else {
> > BUG_ON(ret != -EEXIST);
>
> OK, it seems balance pause/resume logic got broken by dev-replace code
> (5ac00addc7ac09110995fe967071d191b5981cc1), which went into v3.8-rc1.
> This is most certainly not the right way to fix it, that BUG_ON is there
> for a reason. I'll send a fix in a couple of days.
Okay, right here waiting for test ;)
thanks,
liubo
prev parent reply other threads:[~2013-01-16 1:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 14:47 [PATCH] Btrfs: fix crash of starting balance Liu Bo
2013-01-15 16:59 ` Ilya Dryomov
2013-01-16 1:05 ` 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=20130116010529.GC3942@liubo \
--to=bo.li.liu@oracle.com \
--cc=idryomov@gmail.com \
--cc=linux-btrfs@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.