From: Damien Le Moal <dlemoal@kernel.org>
To: "min15.li" <min15.li@samsung.com>,
axboe@kernel.dk, willy@infradead.org, hch@lst.de,
gregkh@linuxfoundation.org, wsa@kernel.org, vkoul@kernel.org
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block: add capacity validation in bdev_add_partition()
Date: Thu, 15 Jun 2023 17:42:48 +0900 [thread overview]
Message-ID: <621fecd9-52ee-b5ba-6702-c283658096ef@kernel.org> (raw)
In-Reply-To: <20230615160929.9240-1-min15.li@samsung.com>
On 6/16/23 01:09, min15.li wrote:
> In the function bdev_add_partition(),there is no check that the start
> and end sectors exceed the size of the disk before calling add_partition.
> When we call the block's ioctl interface directly to add a partition,
> and the capacity of the disk is set to 0 by driver,the command will
> continue to execute.
>
> Signed-off-by: min15.li <min15.li@samsung.com>
> ---
> block/partitions/core.c | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/block/partitions/core.c b/block/partitions/core.c
> index 49e0496ff23c..9806a804e1a4 100644
> --- a/block/partitions/core.c
> +++ b/block/partitions/core.c
> @@ -445,6 +445,12 @@ int bdev_add_partition(struct gendisk *disk, int partno, sector_t start,
> goto out;
> }
>
> + if (start >= get_capacity(disk) ||
> + start + length > get_capacity(disk)) {
declaring:
sector_t capacity = get_capacity(disk);
at the beginning of the function would make this check prettier and fit on one line.
> + ret = -EINVAL;
> + goto out;
> + }
> +
> if (partition_overlaps(disk, start, length, -1)) {
> ret = -EBUSY;
> goto out;
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2023-06-15 8:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20230615081227epcas5p40cd9cdf762fcaeedaa8cf8d92d425560@epcas5p4.samsung.com>
2023-06-15 16:09 ` [PATCH] block: add capacity validation in bdev_add_partition() min15.li
2023-06-15 8:42 ` Damien Le Moal [this message]
2023-06-15 8:44 ` Christoph Hellwig
2023-06-15 8:45 ` 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=621fecd9-52ee-b5ba-6702-c283658096ef@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--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=vkoul@kernel.org \
--cc=willy@infradead.org \
--cc=wsa@kernel.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