Linux Btrfs filesystem development
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Anand Jain <anand.jain@oracle.com>
Cc: 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 15:25:58 +0200	[thread overview]
Message-ID: <20190827132558.GI2752@twin.jikos.cz> (raw)
In-Reply-To: <20190827074045.5563-1-anand.jain@oracle.com>

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.

  parent reply	other threads:[~2019-08-27 13:25 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 [this message]
2019-08-27 13:28   ` Nikolay Borisov
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=20190827132558.GI2752@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