linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: "Gu, Jinxiang" <gujx@cn.fujitsu.com>,
	"dsterba@suse.cz" <dsterba@suse.cz>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH RESEND v4 0/4] device_list_add() peparation to add reappearing missing device
Date: Fri, 20 Apr 2018 14:58:37 +0800	[thread overview]
Message-ID: <d415de04-7e68-c331-b8da-f94bee27579e@oracle.com> (raw)
In-Reply-To: <516DDBE5B1D92D42BCF7A2E37F045A5D01A84EA4B8@G08CNEXMBPEKD02.g08.fujitsu.local>



On 04/20/2018 02:22 PM, Gu, Jinxiang wrote:
> Hi,
> 
> I reproduced this using kernel v4.17-rc1.
> It is not always happens.( occurred times/test times: 1/20)

  Though it was reported here, its not related to this patch set.
  Instead its about the send receive.
  Pls post it as a separate thread so it can be followed up properly.

Thanks, Anand


      reply	other threads:[~2018-04-20  6:56 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-18 14:02 [PATCH RESEND v4 0/4] device_list_add() peparation to add reappearing missing device Anand Jain
2018-01-18 14:02 ` [PATCH 1/4] btrfs: move pr_info into device_list_add Anand Jain
2018-01-18 14:02 ` [PATCH 2/4] btrfs: set the total_devices in device_list_add() Anand Jain
2018-01-18 14:02 ` [PATCH 3/4] btrfs: get device pointer from device_list_add() Anand Jain
2018-01-18 14:02 ` [PATCH 4/4] btrfs: drop devid as device_list_add() arg Anand Jain
2018-01-18 17:47 ` [PATCH RESEND v4 0/4] device_list_add() peparation to add reappearing missing device David Sterba
2018-01-19 23:27   ` David Sterba
2018-01-22 13:31     ` Anand Jain
2018-01-22 15:26       ` David Sterba
2018-01-22 21:52         ` Anand Jain
2018-04-20  6:22           ` Gu, Jinxiang
2018-04-20  6:58             ` Anand Jain [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=d415de04-7e68-c331-b8da-f94bee27579e@oracle.com \
    --to=anand.jain@oracle.com \
    --cc=dsterba@suse.cz \
    --cc=gujx@cn.fujitsu.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).