From: Anand Jain <anand.jain@oracle.com>
To: dsterba@suse.cz, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/2] fix BUG_ON and retun real error in find_next_devid() and clone_fs_devices()
Date: Tue, 10 Sep 2019 16:57:05 +0800 [thread overview]
Message-ID: <981c8121-d639-5bcc-59da-f97e54adee0e@oracle.com> (raw)
In-Reply-To: <031925e7-65a0-0345-8b46-b2e778f50edb@oracle.com>
On 28/8/19 7:12 AM, Anand Jain wrote:
> On 27/8/19 9:25 PM, David Sterba wrote:
>> On Tue, Aug 27, 2019 at 03:40:43PM +0800, Anand Jain wrote:
>>> Fixes BUG_ON in find_next_devid() and fixes to return real error in
>>> clone_fs_devices(). These two patches can be send to be independent.
>>>
>>> Anand Jain (2):
>>> btrfs: fix BUG_ON with proper error handle in find_next_devid
>>> btrfs: fix error return on alloc fail in clone_fs_devices
>>
>> Added to misc-next, thanks.
>
>
>
>> If you have script that can reproduce the
>> problem, please add them to the changelog. I've added more from the
>> discussion and questions from Qu.
>>
>
> The script and output rather makes senses in the patch [1] it doesn't
> here.
> [1] [PATCH v2] btrfs: tree-checker: Fix wrong check on max devid
David,
The script does not make sense in this patch. I still see it in misc-next.
Thanks, Anand
prev parent reply other threads:[~2019-09-10 8:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-27 7:40 [PATCH 0/2] fix BUG_ON and retun real error in find_next_devid() and clone_fs_devices() Anand Jain
2019-08-27 7:40 ` [PATCH 1/2] btrfs: fix BUG_ON with proper error handle in find_next_devid Anand Jain
2019-08-27 8:07 ` Johannes Thumshirn
2019-08-27 8:12 ` Qu Wenruo
2019-08-27 9:58 ` Anand Jain
2019-08-27 11:11 ` Qu Wenruo
2019-08-27 7:40 ` [PATCH 2/2] btrfs: fix error return on alloc fail in clone_fs_devices Anand Jain
2019-08-27 8:12 ` Johannes Thumshirn
2019-08-27 7:59 ` [PATCH 0/2] fix BUG_ON and retun real error in find_next_devid() and clone_fs_devices() Nikolay Borisov
2019-08-27 13:25 ` David Sterba
2019-08-27 13:28 ` Nikolay Borisov
2019-08-27 23:12 ` Anand Jain
2019-09-10 8:57 ` 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=981c8121-d639-5bcc-59da-f97e54adee0e@oracle.com \
--to=anand.jain@oracle.com \
--cc=dsterba@suse.cz \
--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).