mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Zhou, Yun" <yun.zhou@windriver.com>
To: Yu Kuai <yukuai1@huaweicloud.com>, Paul Menzel <pmenzel@molgen.mpg.de>
Cc: agk@redhat.com, snitzer@kernel.org, mpatocka@redhat.com,
	song@kernel.org, dm-devel@lists.linux.dev,
	linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH] md: fix rcu protection in md_wakeup_thread
Date: Wed, 15 Oct 2025 16:19:33 +0800	[thread overview]
Message-ID: <b7e58c57-12be-47d6-beae-aa70568bfcc4@windriver.com> (raw)
In-Reply-To: <e60b45da-e37d-5530-1511-f6e56effebb2@huaweicloud.com>

Hi Kuai,

On 10/15/25 15:57, Yu Kuai wrote:
> CAUTION: This email comes from a non Wind River email account!
> Do not click links or open attachments unless you recognize the sender 
> and know the content is safe.
>
> Hi,
>
> 在 2025/10/15 15:31, Zhou, Yun 写道:
>> This method only changes a little code. But it holds the lock before the
>> function jumps, which seems to violate the principle of minimizing the
>> critical area.
>
> use rcu to protect the function is fine, all related code is not from
> IO fast path.
>
> Please also notice this patch is impossible for stable backport because
> of too much modifications.
>
I will make v2 according to your suggestion.

Thanks,
Yun

      reply	other threads:[~2025-10-15  8:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-15  5:59 Yun Zhou
2025-10-15  6:35 ` Paul Menzel
2025-10-15  6:58   ` Yu Kuai
2025-10-15  7:31     ` Zhou, Yun
2025-10-15  7:57       ` Yu Kuai
2025-10-15  8:19         ` Zhou, Yun [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=b7e58c57-12be-47d6-beae-aa70568bfcc4@windriver.com \
    --to=yun.zhou@windriver.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mpatocka@redhat.com \
    --cc=pmenzel@molgen.mpg.de \
    --cc=snitzer@kernel.org \
    --cc=song@kernel.org \
    --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®