mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Logan Gunthorpe <logang@deltatee.com>
To: Yu Kuai <yukuai1@huaweicloud.com>, song@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	yi.zhang@huawei.com, yangerkun@huawei.com,
	"yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH v3 3/3] md: protect md_thread with rcu
Date: Fri, 31 Mar 2023 09:41:39 -0600	[thread overview]
Message-ID: <825e329f-f18d-7bfd-e8a4-71ee88e17142@deltatee.com> (raw)
In-Reply-To: <f54452de-c5f2-aeab-1218-c0ed3990a481@huaweicloud.com>



On 2023-03-31 00:36, Yu Kuai wrote:

>> Yes, you're right, I'll remove patch 2 and update patch 3. And I'll try
>> to run sparse before sending the new version.
>>
> 
> By the way, I observed lots of sparse errors and warnings for current
> code, will it make sense to fix them?

Yup, I fixed a bunch for raid5 last year. There was one I could not fix
though. I would say effort spent fixing those is well spent.

Thanks!

Logan

      reply	other threads:[~2023-03-31 15:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-30 20:20 [PATCH v3 0/3] md: fix uaf for sync_thread Yu Kuai
2023-03-30 20:20 ` [PATCH v3 1/3] md: pass a md_thread pointer to md_register_thread() Yu Kuai
2023-03-30 20:20 ` [PATCH v3 2/3] md: pass a md_thread pointer to md_wakeup_thread() Yu Kuai
2023-03-30 20:20 ` [PATCH v3 3/3] md: protect md_thread with rcu Yu Kuai
2023-03-30 18:40   ` kernel test robot
2023-03-30 19:35   ` Logan Gunthorpe
2023-03-31  1:08     ` Yu Kuai
2023-03-31  6:36       ` Yu Kuai
2023-03-31 15:41         ` Logan Gunthorpe [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=825e329f-f18d-7bfd-e8a4-71ee88e17142@deltatee.com \
    --to=logang@deltatee.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=song@kernel.org \
    --cc=yangerkun@huawei.com \
    --cc=yi.zhang@huawei.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®