linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Hannes Reinecke <hare@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: Christoph Hellwig <hch@lst.de>, Mike Snitzer <snitzer@kernel.org>,
	linux-block@vger.kernel.org, dm-devel@lists.linux.dev
Subject: Re: [PATCHv2] block: check for max_hw_sectors underflow
Date: Tue, 28 May 2024 11:54:42 +0100	[thread overview]
Message-ID: <acf3e39c-36ae-4792-b870-26d392be5241@oracle.com> (raw)
In-Reply-To: <20240524104651.92506-1-hare@kernel.org>

On 24/05/2024 11:46, Hannes Reinecke wrote:
> The logical block size need to be smaller than the max_hw_sector
> setting, otherwise we can't even transfer a single LBA.
> 
> Signed-off-by: Hannes Reinecke <hare@kernel.org>

Regardless of comment, below:

Reviewed-by: John Garry <john.g.garry@oracle.com>

> ---
>   block/blk-settings.c | 8 ++++++--
>   1 file changed, 6 insertions(+), 2 deletions(-)
> 
> diff --git a/block/blk-settings.c b/block/blk-settings.c
> index d2731843f2fc..030afb597183 100644
> --- a/block/blk-settings.c
> +++ b/block/blk-settings.c
> @@ -104,6 +104,7 @@ static int blk_validate_zoned_limits(struct queue_limits *lim)
>   static int blk_validate_limits(struct queue_limits *lim)
>   {
>   	unsigned int max_hw_sectors;
> +	unsigned int logical_block_sectors;
>   
>   	/*
>   	 * Unless otherwise specified, default to 512 byte logical blocks and a
> @@ -134,8 +135,11 @@ static int blk_validate_limits(struct queue_limits *lim)
>   		lim->max_hw_sectors = BLK_SAFE_MAX_SECTORS;
>   	if (WARN_ON_ONCE(lim->max_hw_sectors < PAGE_SECTORS))
>   		return -EINVAL;
> +	logical_block_sectors = lim->logical_block_size >> SECTOR_SHIFT;
> +	if (WARN_ON_ONCE(logical_block_sectors > lim->max_hw_sectors))
> +		return -EINVAL;
>   	lim->max_hw_sectors = round_down(lim->max_hw_sectors,

I don't think that we ever check if lim->logical_block_size is a 
power-of-2 - but that's a given, right?

> -			lim->logical_block_size >> SECTOR_SHIFT);
> +			logical_block_sectors);
>   
>   	/*
>   	 * The actual max_sectors value is a complex beast and also takes the
> @@ -153,7 +157,7 @@ static int blk_validate_limits(struct queue_limits *lim)
>   		lim->max_sectors = min(max_hw_sectors, BLK_DEF_MAX_SECTORS_CAP);
>   	}
>   	lim->max_sectors = round_down(lim->max_sectors,
> -			lim->logical_block_size >> SECTOR_SHIFT);
> +			logical_block_sectors);
>   
>   	/*
>   	 * Random default for the maximum number of segments.  Driver should not


  parent reply	other threads:[~2024-05-28 10:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24 10:46 [PATCHv2] block: check for max_hw_sectors underflow Hannes Reinecke
2024-05-28  6:29 ` Christoph Hellwig
2024-05-28 10:54 ` John Garry [this message]
2024-05-28 10:58   ` Christoph Hellwig
2024-05-28 13:54     ` John Garry

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=acf3e39c-36ae-4792-b870-26d392be5241@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@lists.linux.dev \
    --cc=hare@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).