mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Garry <john.g.garry@oracle.com>
To: Li Wang <liwang@redhat.com>
Cc: linux-kernel@vger.kernel.org, ltp@lists.linux.it,
	Jan Stancek <jstancek@redhat.com>,
	Damien Le Moal <dlemoal@kernel.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	linux-block@vger.kernel.org, axboe@kernel.dk
Subject: Re: [PATCH] loop: Increase bsize variable from unsigned short to unsigned int
Date: Tue, 27 Aug 2024 08:42:02 +0100	[thread overview]
Message-ID: <d431a0a3-a12d-4da0-b8cb-dd349aee8d4d@oracle.com> (raw)
In-Reply-To: <CAEemH2djkWMtuTN2=Y5MXZVOACeCm32_Hh0zAJxH7X4Ss1MSuQ@mail.gmail.com>

On 27/08/2024 08:35, Li Wang wrote:
> On Tue, Aug 27, 2024 at 3:20 PM John Garry <john.g.garry@oracle.com> wrote:
>>
>> On 27/08/2024 04:22, Li Wang wrote:
>>
>> +linux-block, Jens
>>
>>> This change allows the loopback driver to handle larger block sizes
>>
>> larger than what? PAGE_SIZE?
> 
> Yes, 

Please then explicitly mention that

> system should return EINVAL when the tested bsize is larger than PAGE_SIZE.
> But due to the loop_reconfigure_limits() cast it to 'unsined short' that
 > never gets an expected error when testing invalid logical block size.>
> That's why LTP/ioctl_loop06 failed on a system with 64k (ppc64le) pagesize
> (since kernel-v6.11-rc1 with patches):
> 
>    9423c653fe6110 ("loop: Don't bother validating blocksize")
>    fe3d508ba95bc6 ("block: Validate logical block size in blk_validate_limits()")
> 
> 
> 

I feel that you should be adding a fixes tag, but it seems that those 
commits only expose the issue, and whatever introduced unsigned short 
usage was not right. Maybe you can just get this included for 6.11, 
where 9423c653fe6110 was introduced.

Thanks,
John

  reply	other threads:[~2024-08-27  7:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  3:22 Li Wang
2024-08-27  4:10 ` Damien Le Moal
2024-08-27  5:18 ` Jan Stancek
2024-08-27  7:19 ` John Garry
2024-08-27  7:35   ` Li Wang
2024-08-27  7:42     ` John Garry [this message]
2024-08-27  8:02       ` Li Wang

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=d431a0a3-a12d-4da0-b8cb-dd349aee8d4d@oracle.com \
    --to=john.g.garry@oracle.com \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=jstancek@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=stefanha@redhat.com \
    /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®