From: Jens Axboe <axboe@kernel.dk>
To: willy@infradead.org, hch@lst.de, dlemoal@kernel.org,
gregkh@linuxfoundation.org, Min Li <min15.li@samsung.com>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org, Chaitanya Kulkarni <kch@nvidia.com>
Subject: Re: [PATCH v5] block: add check that partition length needs to be aligned with block size
Date: Wed, 13 Dec 2023 08:20:13 -0700 [thread overview]
Message-ID: <170248081388.44340.415544465517225810.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230629142517.121241-1-min15.li@samsung.com>
On Thu, 29 Jun 2023 14:25:17 +0000, Min Li wrote:
> Before calling add partition or resize partition, there is no check
> on whether the length is aligned with the logical block size.
> If the logical block size of the disk is larger than 512 bytes,
> then the partition size maybe not the multiple of the logical block size,
> and when the last sector is read, bio_truncate() will adjust the bio size,
> resulting in an IO error if the size of the read command is smaller than
> the logical block size.If integrity data is supported, this will also
> result in a null pointer dereference when calling bio_integrity_free.
>
> [...]
Applied, thanks!
[1/1] block: add check that partition length needs to be aligned with block size
commit: 6f64f866aa1ae6975c95d805ed51d7e9433a0016
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-12-13 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230629062728epcas5p2bb48fea42a380039c0eb06c19a44aad1@epcas5p2.samsung.com>
2023-06-29 14:25 ` Min Li
2023-06-29 7:33 ` Christoph Hellwig
[not found] ` <CGME20231016060514epcas5p2ab38287c243a9539736453b4cb34e447@epcas5p2.samsung.com>
2023-10-16 14:03 ` Min Li
2023-12-07 13:24 ` Li Nan
2023-12-13 15:20 ` Jens Axboe [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=170248081388.44340.415544465517225810.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@lst.de \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=min15.li@samsung.com \
--cc=stable@vger.kernel.org \
--cc=willy@infradead.org \
/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®