public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Song Liu <songliubraving@fb.com>
Cc: linux-raid <linux-raid@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	Luis Chamberlain <mcgrof@kernel.org>
Subject: Re: [GIT PULL] md-fixes 20210922
Date: Wed, 22 Sep 2021 12:42:55 -0600	[thread overview]
Message-ID: <b79aae3b-bd40-5f8f-5ecc-873d825f8e46@kernel.dk> (raw)
In-Reply-To: <DE9C1858-5F06-4E1F-A842-19A6B70D3F4F@fb.com>

On 9/22/21 11:38 AM, Song Liu wrote:
> 
> 
>> On Sep 22, 2021, at 9:14 AM, Jens Axboe <axboe@kernel.dk> wrote:
>>
>> On 9/22/21 10:10 AM, Song Liu wrote:
>>> Hi Jens, 
>>>
>>> Please consider pulling the following changes for md-fixes on top of your 
>>> block-5.15 branch. The changes are:
>>>  1. Fix lock order reversal in md_alloc. (Christoph)
>>>  2. Handle add_disk error in md_alloc. (Luis)
>>>  3. Refactor md sysfs attrs, included because of dependency with 1 and 2. 
>>>     (Christoph). 
>>
>> I don't think the error handling for add_disk is prudent at this point,
>> that's something that should go in with the 5.16 cycle. It's been like
>> that forever, nothing that warrants pushing this for 5.15 at all.
> 
> Hmm... I see. The WARN_ON_ONCE at the end of device_add_disk() should be
> enough.

We've had no error handling in add_disk forever, this is not a new issue.


> Then we just need the first commit. Could you please pull the 
> following change instead? 
> 
>   1. Fix lock order reversal in md_alloc. (Christoph)

Looks better, thanks.

-- 
Jens Axboe


      reply	other threads:[~2021-09-22 18:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 16:10 [GIT PULL] md-fixes 20210922 Song Liu
2021-09-22 16:14 ` Jens Axboe
2021-09-22 17:38   ` Song Liu
2021-09-22 18:42     ` Jens Axboe [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=b79aae3b-bd40-5f8f-5ecc-873d825f8e46@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=songliubraving@fb.com \
    /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