From: "Mateusz Jończyk" <mat.jonczyk@o2.pl>
To: Yu Kuai <yukuai1@huaweicloud.com>,
linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: stable@vger.kernel.org, Song Liu <song@kernel.org>,
Paul Luse <paul.e.luse@linux.intel.com>, Xiao Ni <xni@redhat.com>,
Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>,
"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] md/raid1: set max_sectors during early return from choose_slow_rdev()
Date: Sat, 13 Jul 2024 14:40:36 +0200 [thread overview]
Message-ID: <5d698ca4-b6a0-4567-ab6c-899b34293056@o2.pl> (raw)
In-Reply-To: <e9585300-1666-ca71-8684-8824fe2ddaf1@huaweicloud.com>
W dniu 12.07.2024 o 03:16, Yu Kuai pisze:
> Hi,
>
> 在 2024/07/12 4:23, Mateusz Jończyk 写道:
>> Linux 6.9+ is unable to start a degraded RAID1 array with one drive,
>> when that drive has a write-mostly flag set. During such an attempt,
>> the following assertion in bio_split() is hit:
>>
[snip]
>
> Thanks for the patch!
>
> Reviewed-by: Yu Kuai <yukuai3@huawei.com>
>
> BTW, do you have plans to add a new test to mdadm tests? I'll
> pick it up if you don't, just let me know.
>
> Thanks,
> Kuai
Yes, I'm working on it.
Greetings,
Mateusz
prev parent reply other threads:[~2024-07-13 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-06 14:30 [REGRESSION] Cannot start degraded RAID1 array with device with write-mostly flag Mateusz Jończyk
2024-07-07 19:50 ` Mateusz Jończyk
2024-07-08 1:54 ` Yu Kuai
2024-07-08 20:09 ` Mateusz Jończyk
2024-07-09 2:57 ` Yu Kuai
2024-07-11 20:23 ` [PATCH] md/raid1: set max_sectors during early return from choose_slow_rdev() Mateusz Jończyk
2024-07-11 21:14 ` Paul E Luse
2024-07-12 1:16 ` Yu Kuai
2024-07-12 15:11 ` Song Liu
2024-07-13 12:40 ` Mateusz Jończyk [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=5d698ca4-b6a0-4567-ab6c-899b34293056@o2.pl \
--to=mat.jonczyk@o2.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=mariusz.tkaczyk@linux.intel.com \
--cc=paul.e.luse@linux.intel.com \
--cc=song@kernel.org \
--cc=stable@vger.kernel.org \
--cc=xni@redhat.com \
--cc=yukuai1@huaweicloud.com \
--cc=yukuai3@huawei.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
all inboxes | Powered by JetHome®