linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: dsterba@suse.cz, Anand Jain <anand.jain@oracle.com>,
	linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2] btrfs: cleanup assigning next active device with a check
Date: Wed, 4 May 2016 10:44:40 +0200	[thread overview]
Message-ID: <20160504084440.GN29353@twin.jikos.cz> (raw)
In-Reply-To: <20160503174728.GM29353@twin.jikos.cz>

On Tue, May 03, 2016 at 07:47:28PM +0200, David Sterba wrote:
> On Tue, May 03, 2016 at 06:01:31PM +0800, Anand Jain wrote:
> > 
> > 
> > On 05/02/2016 11:26 PM, David Sterba wrote:
> > > On Mon, May 02, 2016 at 07:02:08AM +0800, Anand Jain wrote:
> > >> --- a/fs/btrfs/dev-replace.c
> > >> +++ b/fs/btrfs/dev-replace.c
> > >> @@ -569,11 +569,9 @@ static int btrfs_dev_replace_finishing(struct btrfs_fs_info *fs_info,
> > >>   	ASSERT(list_empty(&src_device->resized_list));
> > >>   	tgt_device->commit_total_bytes = src_device->commit_total_bytes;
> > >>   	tgt_device->commit_bytes_used = src_device->bytes_used;
> > >> -	if (fs_info->sb->s_bdev &&
> > >> -		(fs_info->sb->s_bdev == src_device->bdev))
> > >> -		fs_info->sb->s_bdev = tgt_device->bdev;
> > >
> > > What's the base of this patch?
> > 
> >   It was on master. But now the V3 which is based on your for-next.
> > 
> > > The above code is not in my for-next so
> > > I could be missing some important bits.
> > 
> >   Yes. That was added by this patch.
> > 
> >   [PATCH] btrfs: s_bdev is not null after missing replace
> 
> Ah, that's the one. Added to next together with v3, though a testcase is
> still desirable.

There were some merge conflicts with the dev-del-by-id patchset so I've
put the patches there.

  parent reply	other threads:[~2016-05-04  8:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-18 11:25 [PATCH] btrfs: cleanup assigning next active device with a check Anand Jain
2016-04-25 15:15 ` David Sterba
2016-05-01 23:05   ` Anand Jain
2016-05-01 23:02 ` [PATCH v2] " Anand Jain
2016-05-02 15:26   ` David Sterba
2016-05-03 10:01     ` Anand Jain
2016-05-03 17:47       ` David Sterba
2016-05-03 23:31         ` Anand Jain
2016-05-04  9:00           ` David Sterba
2016-05-04  8:44         ` David Sterba [this message]
2016-05-03  9:44 ` [PATCH] " Anand Jain

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=20160504084440.GN29353@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=anand.jain@oracle.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 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).