public inbox for linux-raid@vger.kernel.org
 help / color / mirror / Atom feed
From: "heming.zhao@suse.com" <heming.zhao@suse.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-raid@vger.kernel.org, song@kernel.org,
	guoqing.jiang@cloud.ionos.com, lidong.zhong@suse.com,
	xni@redhat.com, neilb@suse.de, colyli@suse.com
Subject: Re: [PATCH v2] md: don't create mddev in md_open
Date: Thu, 1 Apr 2021 21:01:05 +0800	[thread overview]
Message-ID: <a96554cc-abbd-347c-ea24-37d2a41e6073@suse.com> (raw)
In-Reply-To: <20210401061722.GA1355765@infradead.org>

On 4/1/21 2:17 PM, Christoph Hellwig wrote:
> On Thu, Apr 01, 2021 at 09:34:56AM +0800, Zhao Heming wrote:
>> commit d3374825ce57 ("md: make devices disappear when they are no longer
>> needed.") introduced protection between mddev creating & removing. The
>> md_open shouldn't create mddev when all_mddevs list doesn't contain
>> mddev. With currently code logic, there will be very easy to trigger
>> soft lockup in non-preempt env.
> 
> As mention below, please don't make this even more of a mess than it
> needs to.  We can just pick the two patches doing this from the series
> I sent:
> 

Hi,

I already got your meaning on previously email.
I sent v2 patch for Song's review comment. My patch is bugfix, it may need
to back port into branch maintenance.

Your attachment patch files is partly my patch.
The left part is in md_open (response [PATCH 01/15] md: remove the code to flush
an old instance in md_open)
I still think you directly use bdev->bd_disk->private_data as mddev pointer is not safe.

Let's wait for other guys opinions.

Thanks,
heming


  reply	other threads:[~2021-04-01 18:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-01  1:34 [PATCH v2] md: don't create mddev in md_open Zhao Heming
2021-04-01  6:17 ` Christoph Hellwig
2021-04-01 13:01   ` heming.zhao [this message]
2021-04-02  5:58     ` Song Liu
2021-04-02 10:48       ` Christoph Hellwig
     [not found]       ` <b2288ab4-1da0-612d-8988-637cc33db99a@suse.com>
2021-04-02 16:01         ` Song Liu
2021-04-03  2:45           ` heming.zhao

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=a96554cc-abbd-347c-ea24-37d2a41e6073@suse.com \
    --to=heming.zhao@suse.com \
    --cc=colyli@suse.com \
    --cc=guoqing.jiang@cloud.ionos.com \
    --cc=hch@infradead.org \
    --cc=lidong.zhong@suse.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=song@kernel.org \
    --cc=xni@redhat.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