Linux RAID subsystem development
 help / color / mirror / Atom feed
From: junxiao.bi@oracle.com
To: Logan Gunthorpe <logang@deltatee.com>, linux-raid@vger.kernel.org
Cc: song@kernel.org, yukuai1@huaweicloud.com
Subject: Re: [PATCH 2/2] md: bypass block throttle for superblock update
Date: Tue, 7 Nov 2023 13:11:54 -0800	[thread overview]
Message-ID: <36fb534d-dac7-4480-94a5-976bcd58ec59@oracle.com> (raw)
In-Reply-To: <9b95971b-ac76-46d4-83b8-aa1f67c6c0c9@deltatee.com>

On 11/7/23 11:33 AM, Logan Gunthorpe wrote:

>
> On 2023-11-07 10:57, Junxiao Bi wrote:
>> commit 5e2cf333b7bd ("md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d")
>> introduced a hung bug and got reverted in last patch, since the issue
>> that commit is fixing is due to md superblock write is throttled by wbt,
>> to fix it, we can have superblock write bypass block layer throttle.
>>
>> Fixes: 5e2cf333b7bd ("md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d")
>> Suggested-by: Yu Kuai <yukuai1@huaweicloud.com>
>> Signed-off-by: Junxiao Bi <junxiao.bi@oracle.com>
> This makes sense to me. However, I haven't looked at that bug in a long
> time though and I haven't tested the proposed solution to ensure the bug
> is indeed fixed.
>
> Would it not make sense to have the fixing commit first before the
> revert? So there isn't a spot in the history with a known bug?

Yea, that makes sense.

Thanks for the review.

>
> Besides that,
>
> Reviewed-by: Logan Gunthorpe <logang@deltatee.com>
>
> Thanks!
>
> Logan

      reply	other threads:[~2023-11-07 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-07 17:57 [PATCH 1/2] Revert "md/raid5: Wait for MD_SB_CHANGE_PENDING in raid5d" Junxiao Bi
2023-11-07 17:57 ` [PATCH 2/2] md: bypass block throttle for superblock update Junxiao Bi
2023-11-07 19:33   ` Logan Gunthorpe
2023-11-07 21:11     ` junxiao.bi [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=36fb534d-dac7-4480-94a5-976bcd58ec59@oracle.com \
    --to=junxiao.bi@oracle.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=song@kernel.org \
    --cc=yukuai1@huaweicloud.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