Linux block layer
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Min Li <min15.li@samsung.com>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"axboe@kernel.dk" <axboe@kernel.dk>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"hch@lst.de" <hch@lst.de>,
	"willy@infradead.org" <willy@infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v4] block: add check that partition length needs to be aligned with block size
Date: Thu, 29 Jun 2023 03:13:17 +0000	[thread overview]
Message-ID: <79eabfb0-3c90-354b-a02b-0d2fddeeb358@nvidia.com> (raw)
In-Reply-To: <fe796add-74f6-5b52-69b3-4823b93cd54c@kernel.org>

On 6/28/2023 7:38 PM, Damien Le Moal wrote:
> On 6/29/23 19:26, 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.
>>
>> Cc: stable@vger.kernel.org
>> Signed-off-by: Min Li <min15.li@samsung.com>>
>> ---
>> Changes from v1:
>>
>> - Add a space after /* and before */.
>> - Move length alignment check before the "start = p.start >> SECTOR_SHIFT"
>> - Move check for p.start being aligned together with this length alignment check.
>>
>> Changes from v2:
>>
>> - Add the assignment on the first line and merge the two lines into one.
>>
>> Changes from v3:
>>
>> - Change the blksz to unsigned int.
>> - Add check if p.start and p.length are negative.
>> ---
>>   block/ioctl.c | 12 ++++++++----
>>   1 file changed, 8 insertions(+), 4 deletions(-)
>>
>> diff --git a/block/ioctl.c b/block/ioctl.c
>> index 3be11941fb2d..a8061c2fcae0 100644
>> --- a/block/ioctl.c
>> +++ b/block/ioctl.c
>> @@ -16,9 +16,10 @@
>>   static int blkpg_do_ioctl(struct block_device *bdev,
>>   			  struct blkpg_partition __user *upart, int op)
>>   {
>> +	unsigned int blksz = bdev_logical_block_size(bdev);
>>   	struct gendisk *disk = bdev->bd_disk;
>>   	struct blkpg_partition p;
>> -	long long start, length;
>> +	sector_t start, length;
>>   
>>   	if (!capable(CAP_SYS_ADMIN))
>>   		return -EACCES;
>> @@ -33,14 +34,17 @@ static int blkpg_do_ioctl(struct block_device *bdev,
>>   	if (op == BLKPG_DEL_PARTITION)
>>   		return bdev_del_partition(disk, p.pno);
>>   
>> +	if (p.start < 0 || p.length <= 0 || p.start + p.length < 0)
>> +		return -EINVAL;
>> +	/* Check that the partition is aligned to the block size */
>> +	if (!IS_ALIGNED(p.start | p.length, blksz))
> 
> Minor nit: blksz is used only here now, so this could be changed to:
> 
> 	if (!IS_ALIGNED(p.start | p.length, bdev_logical_block_size(bdev)))
> 
> to not use that local variable.
> 
> With or without this addressed, looks good to me.
> 
> Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
> 
>

With above comment addressed,

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck




      reply	other threads:[~2023-06-29  3:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20230629022807epcas5p23765f81f547eed72135c802f83543908@epcas5p2.samsung.com>
2023-06-29 10:26 ` [PATCH v4] block: add check that partition length needs to be aligned with block size Min Li
2023-06-29  2:38   ` Damien Le Moal
2023-06-29  3:13     ` Chaitanya Kulkarni [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=79eabfb0-3c90-354b-a02b-0d2fddeeb358@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hch@lst.de \
    --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