From: Sasha Levin <sashal@kernel.org>
To: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
Damien Le Moal <dlemoal@kernel.org>,
Johannes Thumshirn <Johannes.Thumshirn@wdc.com>,
Jens Axboe <axboe@kernel.dk>, "kch@nvidia.com" <kch@nvidia.com>,
"yanjun.zhu@linux.dev" <yanjun.zhu@linux.dev>,
"zhengqixing@huawei.com" <zhengqixing@huawei.com>,
"yukuai3@huawei.com" <yukuai3@huawei.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"hare@suse.de" <hare@suse.de>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH AUTOSEL 6.14 29/54] null_blk: replace null_process_cmd() call in null_zone_write()
Date: Sun, 13 Apr 2025 20:12:18 -0400 [thread overview]
Message-ID: <Z_xS4iiTNPJ5mP0-@lappy> (raw)
In-Reply-To: <qytrsydugyz3ksuzg4m3aznskweuhphm7nkhm2faks3oefc7ok@jmteb2yigxj5>
On Fri, Apr 04, 2025 at 03:31:03AM +0000, Shinichiro Kawasaki wrote:
>On Apr 03, 2025 / 15:01, Sasha Levin wrote:
>> From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
>>
>> [ Upstream commit 4f235000b1e88934d1e6117dc43ed814710ef4e2 ]
>>
>> As a preparation to support partial data transfer due to badblocks,
>> replace the null_process_cmd() call in null_zone_write() with equivalent
>> calls to null_handle_badblocks() and null_handle_memory_backed(). This
>> commit does not change behavior. It will enable null_handle_badblocks()
>> to return the size of partial data transfer in the following commit,
>> allowing null_zone_write() to move write pointers appropriately.
>
>Hello Sasha, I don't think this patch should be in stable kernels, since it
>just refactors code as a preparation for another patch. I suggest to drop it
>for all stable kernels.
I'll drop it, thanks!
--
Thanks,
Sasha
prev parent reply other threads:[~2025-04-14 0:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250403190209.2675485-1-sashal@kernel.org>
2025-04-03 19:01 ` [PATCH AUTOSEL 6.14 29/54] null_blk: replace null_process_cmd() call in null_zone_write() Sasha Levin
2025-04-04 3:31 ` Shinichiro Kawasaki
2025-04-14 0:12 ` Sasha Levin [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=Z_xS4iiTNPJ5mP0-@lappy \
--to=sashal@kernel.org \
--cc=Johannes.Thumshirn@wdc.com \
--cc=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hare@suse.de \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=shinichiro.kawasaki@wdc.com \
--cc=stable@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
--cc=yukuai3@huawei.com \
--cc=zhengqixing@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).