From: Wang Jinchao <wangjinchao600@gmail.com>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org,
Song Liu <song@kernel.org>, "yukuai (C)" <yukuai3@huawei.com>
Subject: Re: [PATCH v2] md/raid1: Fix stack memory use after return in raid1_reshape
Date: Wed, 18 Jun 2025 19:47:13 +0800 [thread overview]
Message-ID: <d6481ddf-67e3-41ed-8ecf-d11ffdc6f4aa@gmail.com> (raw)
In-Reply-To: <d7022eb3-4dee-8d15-1018-051b882467b2@huaweicloud.com>
On 6/16/25 19:32, Yu Kuai wrote:
> Hi,
>
> 在 2025/06/16 18:11, Wang Jinchao 写道:
>> On 6/13/25 19:53, Wang Jinchao wrote:
>>> On 2025/6/13 17:15, Yu Kuai wrote:
>>>> Hi,
>>>>
>>>> 在 2025/06/12 20:21, Wang Jinchao 写道:
>>>>> BTW, I feel raid1_reshape can be better coding with following:
>>>>
>>>> And another hint:
>>>>
>>>> The poolinfo can be removed directly, the only other place to use it
>>>> is r1buf_pool, and can covert to pass in conf or &conf->raid_disks.
>>> Thanks, I'll review these relationships carefully before refactoring.
>>>>
>>>> Thanks,
>>>> Kuai
>>>>
Hi,
I’ve changed r1bio_pool to a pointer type and sent the patch.
As for the other two optimization suggestions, I found it challenging
to implement proper error rollback after the changes.
I tried a few times but couldn't come up with code I’m happy with,
so I’ve decided to put it on hold for now.
Thanks for your guidance.
>> .
>>
>
prev parent reply other threads:[~2025-06-18 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-11 8:55 [PATCH v2] md/raid1: Fix stack memory use after return in raid1_reshape Wang Jinchao
2025-06-12 7:31 ` Yu Kuai
2025-06-12 7:45 ` Wang Jinchao
2025-06-12 9:17 ` Yu Kuai
2025-06-12 9:55 ` Wang Jinchao
2025-06-12 11:23 ` Yu Kuai
2025-06-12 11:46 ` Wang Jinchao
2025-06-12 11:58 ` Yu Kuai
2025-06-12 12:21 ` Wang Jinchao
2025-06-13 9:15 ` Yu Kuai
2025-06-13 11:53 ` Wang Jinchao
2025-06-16 10:11 ` Wang Jinchao
2025-06-16 11:32 ` Yu Kuai
2025-06-18 11:47 ` Wang Jinchao [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=d6481ddf-67e3-41ed-8ecf-d11ffdc6f4aa@gmail.com \
--to=wangjinchao600@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.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;
as well as URLs for NNTP newsgroup(s).