From: Damien Le Moal <damien.lemoal@opensource.wdc.com>
To: Tadeusz Struk <tadeusz.struk@linaro.org>, stable@vger.kernel.org
Cc: axboe@kernel.dk, hch@lst.de, linux-block@vger.kernel.org,
linux-kernel@vger.kernel.org,
syzbot+662448179365dddc1880@syzkaller.appspotmail.com,
xieyongji@bytedance.com
Subject: Re: [PATCH 5.15] block: Add a helper to validate the block size
Date: Fri, 19 Nov 2021 11:53:21 +0900 [thread overview]
Message-ID: <68ff6cd4-41f7-59e7-300e-566be26f26f0@opensource.wdc.com> (raw)
In-Reply-To: <debb322e-395d-90a9-2052-0cf69d96f024@linaro.org>
On 2021/11/19 11:41, Tadeusz Struk wrote:
> On 11/18/21 17:55, Damien Le Moal wrote:
>> But where is this used in 5.15 ? I do not see any callers for this.
>> So why backport it ?
> It will be used after the
> af3c570fb0df ("loop: Use blk_validate_block_size() to validate block size")
> is applied.
> Please read the first message in the thread to get the context.
None of the patches in that series are marked for stable. If you want all of
them backported, sending all patches together as a series would make things
easier to understand.
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2021-11-19 2:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 23:08 general protection fault in bdev_read_page Tadeusz Struk
2021-11-18 23:57 ` [PATCH 5.15] block: Add a helper to validate the block size Tadeusz Struk
2021-11-19 1:55 ` Damien Le Moal
2021-11-19 2:41 ` Tadeusz Struk
2021-11-19 2:53 ` Damien Le Moal [this message]
2021-11-18 23:57 ` [PATCH 5.14] " Tadeusz Struk
2021-11-18 23:58 ` [PATCH 5.10] " Tadeusz Struk
2021-11-19 12:45 ` general protection fault in bdev_read_page Greg KH
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=68ff6cd4-41f7-59e7-300e-566be26f26f0@opensource.wdc.com \
--to=damien.lemoal@opensource.wdc.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=syzbot+662448179365dddc1880@syzkaller.appspotmail.com \
--cc=tadeusz.struk@linaro.org \
--cc=xieyongji@bytedance.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).