From: Christoph Hellwig <hch@infradead.org>
To: Song Liu <song@kernel.org>
Cc: "heming.zhao@suse.com" <heming.zhao@suse.com>,
Christoph Hellwig <hch@infradead.org>,
linux-raid <linux-raid@vger.kernel.org>,
Guoqing Jiang <guoqing.jiang@cloud.ionos.com>,
lidong.zhong@suse.com, Xiao Ni <xni@redhat.com>,
NeilBrown <neilb@suse.de>, Coly Li <colyli@suse.com>
Subject: Re: [PATCH v2] md: don't create mddev in md_open
Date: Fri, 2 Apr 2021 11:48:11 +0100 [thread overview]
Message-ID: <20210402104811.GA1798339@infradead.org> (raw)
In-Reply-To: <CAPhsuW6_9av6H=1LkD5qqpyOcA8j2jj8d660FUpadn3Jfd79Vw@mail.gmail.com>
On Thu, Apr 01, 2021 at 10:58:54PM -0700, Song Liu wrote:
> Hi Christoph and Heming,
>
> Trying to understand the whole picture here. Please let me know if I
> misunderstood anything.
>
> IIUC, the primary goal of Christoph's set is to get rid of the
> ERESTARTSYS hack from md,
> and eventually move bd_mutext. 02/15 to 07/15 of this set cleans up
> code in md.c, and they
> are not very important for the rest of the set (is this correct?).
Yes, at least that is the long term goal.
But as posted in this thread we can just split the two patches out
to do the same thing that the patch from Heming did, without making more
of a mess of mddev_find. I can resend them separately as a small series
instead of the attachment if that makes them easier to review.
next prev parent reply other threads:[~2021-04-02 10:48 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
2021-04-02 5:58 ` Song Liu
2021-04-02 10:48 ` Christoph Hellwig [this message]
[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=20210402104811.GA1798339@infradead.org \
--to=hch@infradead.org \
--cc=colyli@suse.com \
--cc=guoqing.jiang@cloud.ionos.com \
--cc=heming.zhao@suse.com \
--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