Linux Test Project
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Luis Chamberlain <mcgrof@kernel.org>,
	Christoph Hellwig <hch@lst.de>,
	ltp@lists.linux.it, Hannes Reinecke <hare@suse.de>
Subject: Re: [LTP] [PATCH v4] ioctl_loop06: update loopback block size validation
Date: Fri, 14 Mar 2025 14:48:16 +0100	[thread overview]
Message-ID: <20250314134816.GA465459@pevik> (raw)
In-Reply-To: <20250314115848.173676-1-liwang@redhat.com>

Hi Li,

> The kernel commit 47dd6753 ("block/bdev: lift block size restrictions to 64k")
> now supports block sizes larger than PAGE_SIZE, with a new upper limit of
> BLK_MAX_BLOCK_SIZE (64K). But ioctl_loop06 still assumes that PAGE_SIZE is the
> maximum allowed block size, causing failures on newer kernels(>= 6.14):

>   ioctl_loop06.c:74: TINFO: Using LOOP_SET_BLOCK_SIZE with arg > PAGE_SIZE
>   ioctl_loop06.c:57: TFAIL: Set block size succeed unexpectedly
>   ...
>   ioctl_loop06.c:74: TINFO: Using LOOP_CONFIGURE with block_size > PAGE_SIZE
>   ioctl_loop06.c:57: TFAIL: Set block size succeed unexpectedly

> This patch updates ioctl_loop06 to use BLK_MAX_BLOCK_SIZE instead of PAGE_SIZE
> for block size validation.

> And, dynamically sets bs based on BLK_MAX_BLOCK_SIZE, using 1024 bytes if it's
> below 1MB or scaling it otherwise. Ensures tst_fill_file() writes efficiently
> while maintaining compatibility across different kernel versions.

LGTM.
Reviewed-by: Petr Vorel <pvorel@suse.cz>

Kind regards,
Petr

-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2025-03-14 13:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13  9:24 [LTP] [PATCH v2] ioctl_loop06: update loopback block size validation Li Wang
2025-03-13 22:59 ` Luis Chamberlain via ltp
2025-03-14  2:24   ` Li Wang
2025-03-14  2:31     ` [LTP] [PATCH v3] " Li Wang
2025-03-14 11:58       ` [LTP] [PATCH v4] " Li Wang
2025-03-14 13:48         ` Petr Vorel [this message]
2025-04-11  8:38         ` Avinesh Kumar
2025-04-11 10:08           ` Li Wang via ltp
2025-03-14  5:52     ` [LTP] [PATCH v2] " Luis Chamberlain via ltp
2025-03-14  5:57       ` Luis Chamberlain via ltp
2025-03-14  6:49         ` Li Wang
2025-03-14  6:47       ` 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=20250314134816.GA465459@pevik \
    --to=pvorel@suse.cz \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=liwang@redhat.com \
    --cc=ltp@lists.linux.it \
    --cc=mcgrof@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