From: Nikolay Borisov <nborisov@suse.com>
To: dsterba@suse.cz, Anand Jain <anand.jain@oracle.com>,
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, 27 Aug 2019 16:28:00 +0300 [thread overview]
Message-ID: <c4d17e9c-4de9-7195-583c-6f5c2261d815@suse.com> (raw)
In-Reply-To: <20190827132558.GI2752@twin.jikos.cz>
On 27.08.19 г. 16:25 ч., 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.
>
Actually such a script should ideally be turned into an fstest testcase
next prev parent reply other threads:[~2019-08-27 13:28 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 [this message]
2019-08-27 23:12 ` Anand Jain
2019-09-10 8:57 ` 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=c4d17e9c-4de9-7195-583c-6f5c2261d815@suse.com \
--to=nborisov@suse.com \
--cc=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).