From: Song Liu <songliubraving@fb.com>
To: Logan Gunthorpe <logang@deltatee.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-raid <linux-raid@vger.kernel.org>,
David Sloan <david.sloan@eideticom.com>,
Yu Kuai <yukuai3@huawei.com>,
Mateusz Grzonka <mateusz.grzonka@intel.com>,
Saurabh Sengar <ssengar@linux.microsoft.com>,
XU pengfei <xupengfei@nfschina.com>,
Guoqing Jiang <guoqing.jiang@linux.dev>,
Zhou nan <zhounan@nfschina.com>
Subject: Re: [GIT PULL] md-next 20220921
Date: Thu, 22 Sep 2022 00:40:29 +0000 [thread overview]
Message-ID: <2633E2B7-A522-4FD7-B8DE-CF6631CBAF8B@fb.com> (raw)
In-Reply-To: <80560b23-c124-c8ce-d66b-a7afe5b7fa41@deltatee.com>
Hi Logan,
> On Sep 21, 2022, at 4:44 PM, Logan Gunthorpe <logang@deltatee.com> wrote:
>
> On 2022-09-21 16:37, Logan Gunthorpe wrote:
>>
>>
>> On 2022-09-21 15:33, Song Liu wrote:
>>> Hi Jens,
>>>
>>> Please consider pulling the following changes for md-next on top of your
>>> for-6.1/block branch (for-6.1/drivers branch doesn't exist yet).
>>>
>>> The major changes are:
>>>
>>> 1. Various raid5 fix and clean up, by Logan Gunthorpe and David Sloan.
>>> 2. Raid10 performance optimization, by Yu Kuai.
>>> 3. Generate CHANGE uevents for md device, by Mateusz Grzonka.
>>
>> I may have hit a bug with my tests on the latest md-next branch. Still
>> trying to hit it again. The last tests I ran for several days with some
>> patches on the previous md-next branch, but I didn't have Mateusz's
>> changes, and it also looks like the branch was rebased today so it could
>> be caused by either of those things. I'll let you know when I know more.
>
> Yes, ok, I've found two separate issues and both are fixed by reverting
>
> 21023a82bff7 ("md: generate CHANGE uevents for md device")
>
> I suggest we drop that patch for this cycle so we can sort them out.
>
> The issues are:
>
> 1) The concrete issue comes when running mdadm test 01r1fail. I get the
> kernel bugs at the end of this email. It seems we cannot call
> kobject_uevent() in at least one of the contexts that md_new_event() is
> called in because it sleeps in a critical section.
>
> 2) With our custom test suite that creates and destroys arrays, adds and
> removes disks, and runs data through them repeatedly, I randomly start
> seeing these warnings:
>
> mdadm: Fail to create md0 when using
> /sys/module/md_mod/parameters/new_array, fallback to creation via node
>
> And then very occasionally get that warning paired with this error:
>
> mdadm: unexpected failure opening /dev/md0
>
> Which stops the test because it fails to create an array. I also see a
> lot of the same bugs as below so it may be related.
Thanks for testing and debugging these issues. I also see issue 1).
Jens, please ignore this pull request. I will send v2 later.
Song
prev parent reply other threads:[~2022-09-22 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 21:33 [GIT PULL] md-next 20220921 Song Liu
2022-09-21 22:37 ` Logan Gunthorpe
2022-09-21 23:44 ` Logan Gunthorpe
2022-09-22 0:40 ` Song Liu [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=2633E2B7-A522-4FD7-B8DE-CF6631CBAF8B@fb.com \
--to=songliubraving@fb.com \
--cc=axboe@kernel.dk \
--cc=david.sloan@eideticom.com \
--cc=guoqing.jiang@linux.dev \
--cc=linux-raid@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=mateusz.grzonka@intel.com \
--cc=ssengar@linux.microsoft.com \
--cc=xupengfei@nfschina.com \
--cc=yukuai3@huawei.com \
--cc=zhounan@nfschina.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