[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240705123842.GA29995@lst.de>
Date: Fri, 5 Jul 2024 14:38:42 +0200
From: Christoph Hellwig <hch@....de>
To: John Garry <john.g.garry@...cle.com>
Cc: Christoph Hellwig <hch@....de>, axboe@...nel.dk, mst@...hat.com,
jasowang@...hat.com, xuanzhuo@...ux.alibaba.com,
eperezma@...hat.com, pbonzini@...hat.com, stefanha@...hat.com,
hare@...e.de, kbusch@...nel.org, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, virtualization@...ts.linux.dev
Subject: Re: [PATCH 2/5] block: Validate logical block size in
blk_validate_limits()
On Fri, Jul 05, 2024 at 01:34:37PM +0100, John Garry wrote:
>> This should print a message. Unfortunately we don't have the device
>> name here (for that we'd need to set it at disk/queue allocation time,
>> which will require a bit of work), but even without that it will be
>> very useful.
>
> Ok, I can print a message, like:
>
> pr_warn("Invalid logical block size (%d)\n", bsize);
>
> I am wary though that userspace could trigger this message from the various
> ioctls to set the bsize.
As anything ending up here is a configuration interface, such a message
should be perfectly fine.
Powered by blists - more mailing lists