linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Joanne Koong <joannelkoong@gmail.com>
Cc: brauner@kernel.org, djwong@kernel.org, hch@infradead.org,
	linux-fsdevel@vger.kernel.org, syzbot@syzkaller.appspotmail.com
Subject: Re: [PATCH] iomap: adjust read range correctly for non-block-aligned positions
Date: Thu, 25 Sep 2025 09:46:30 -0400	[thread overview]
Message-ID: <aNVHtoCIJOOG966b@bfoster> (raw)
In-Reply-To: <20250922180042.1775241-1-joannelkoong@gmail.com>

On Mon, Sep 22, 2025 at 11:00:42AM -0700, Joanne Koong wrote:
> iomap_adjust_read_range() assumes that the position and length passed in
> are block-aligned. This is not always the case however, as shown in the
> syzbot generated case for erofs. This causes too many bytes to be
> skipped for uptodate blocks, which results in returning the incorrect
> position and length to read in. If all the blocks are uptodate, this
> underflows length and returns a position beyond the folio.
> 
> Fix the calculation to also take into account the block offset when
> calculating how many bytes can be skipped for uptodate blocks.
> 
> Signed-off-by: Joanne Koong <joannelkoong@gmail.com>
> Tested-by: syzbot@syzkaller.appspotmail.com
> ---

Reviewed-by: Brian Foster <bfoster@redhat.com>

>  fs/iomap/buffered-io.c | 19 +++++++++++++------
>  1 file changed, 13 insertions(+), 6 deletions(-)
> 
> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
> index 8b847a1e27f1..1c95a0a7b302 100644
> --- a/fs/iomap/buffered-io.c
> +++ b/fs/iomap/buffered-io.c
> @@ -240,17 +240,24 @@ static void iomap_adjust_read_range(struct inode *inode, struct folio *folio,
>  	 * to avoid reading in already uptodate ranges.
>  	 */
>  	if (ifs) {
> -		unsigned int i;
> +		unsigned int i, blocks_skipped;
>  
>  		/* move forward for each leading block marked uptodate */
> -		for (i = first; i <= last; i++) {
> +		for (i = first; i <= last; i++)
>  			if (!ifs_block_is_uptodate(ifs, i))
>  				break;
> -			*pos += block_size;
> -			poff += block_size;
> -			plen -= block_size;
> -			first++;
> +
> +		blocks_skipped = i - first;
> +		if (blocks_skipped) {
> +			unsigned long block_offset = *pos & (block_size - 1);
> +			unsigned bytes_skipped =
> +				(blocks_skipped << block_bits) - block_offset;
> +
> +			*pos += bytes_skipped;
> +			poff += bytes_skipped;
> +			plen -= bytes_skipped;
>  		}
> +		first = i;
>  
>  		/* truncate len if we find any trailing uptodate block(s) */
>  		while (++i <= last) {
> -- 
> 2.47.3
> 


  parent reply	other threads:[~2025-09-25 13:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 18:00 [PATCH] iomap: adjust read range correctly for non-block-aligned positions Joanne Koong
2025-09-22 18:21 ` Christoph Hellwig
2025-09-25 13:46 ` Brian Foster [this message]
2025-09-29  9:35 ` Christian Brauner

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=aNVHtoCIJOOG966b@bfoster \
    --to=bfoster@redhat.com \
    --cc=brauner@kernel.org \
    --cc=djwong@kernel.org \
    --cc=hch@infradead.org \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=syzbot@syzkaller.appspotmail.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;
as well as URLs for NNTP newsgroup(s).