From: John Garry <john.g.garry@oracle.com>
To: Li Wang <liwang@redhat.com>,
linux-kernel@vger.kernel.org, linux-block@vger.kernel.org,
axboe@kernel.dk, ltp@lists.linux.it
Cc: Stefan Hajnoczi <stefanha@redhat.com>,
Damien Le Moal <dlemoal@kernel.org>,
Jan Stancek <jstancek@redhat.com>
Subject: Re: [PATCh v2] loop: Increase bsize variable from unsigned short to unsigned int
Date: Tue, 27 Aug 2024 09:40:53 +0100 [thread overview]
Message-ID: <b9f2ae40-7c13-4d43-b97e-fe011688a14a@oracle.com> (raw)
In-Reply-To: <20240827081757.37646-1-liwang@redhat.com>
On 27/08/2024 09:17, Li Wang wrote:
> This change allows the loopback driver to handle block size larger than
> PAGE_SIZE and increases the consistency of data types used within the driver.
> Especially to match the struct queue_limits.logical_block_size type.
>
> Also, this is to get rid of the LTP/ioctl_loop06 test failure:
>
> 12 ioctl_loop06.c:76: TINFO: Using LOOP_SET_BLOCK_SIZE with arg > PAGE_SIZE
> 13 ioctl_loop06.c:59: TFAIL: Set block size succeed unexpectedly
> ...
> 18 ioctl_loop06.c:76: TINFO: Using LOOP_CONFIGURE with block_size > PAGE_SIZE
> 19 ioctl_loop06.c:59: TFAIL: Set block size succeed unexpectedly
>
> Thoese fail due to the loop_reconfigure_limits() cast bsize to 'unsined short'
these
> that never gets an expected error when testing invalid logical block size,
> which was just exposed since 6.11-rc1 introduced patches:
>
> commit 9423c653fe61 ("loop: Don't bother validating blocksize")
> commit fe3d508ba95b ("block: Validate logical block size in blk_validate_limits()")
Maybe it's better to add a fixes tag for original commit which
introduced unsigned short usage.
>
> Link:https://urldefense.com/v3/__https://lists.linux.it/pipermail/ltp/2024-
> August/039912.html__;!!ACWV5N9M2RV99hQ!
> MxW7Cvs_YKyihvENQFEGgHt-1KbCFD9gkUJxwI8gguQlawan3UNneBoB_THVG4zNP8Sao2a0apcOu03lcg$
> Signed-off-by: Li Wang<liwang@redhat.com>
> Cc: John Garry<john.g.garry@oracle.com>
> Cc: Jens Axboe<axboe@kernel.dk>
> Cc: Stefan Hajnoczi<stefanha@redhat.com>
> Reviewed-by: Damien Le Moal<dlemoal@kernel.org>
> Reviewed-by: Jan Stancek<jstancek@redhat.com>
Reviewed-by: John Garry <john.g.garry@oracle.com>
next prev parent reply other threads:[~2024-08-27 8:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 8:17 Li Wang
2024-08-27 8:40 ` John Garry [this message]
2024-08-27 11:59 ` 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=b9f2ae40-7c13-4d43-b97e-fe011688a14a@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®