From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-block@vger.kernel.org,
syzbot+0a3683a0a6fecf909244@syzkaller.appspotmail.com
Subject: Re: [PATCH] block: refine the EOF check in blkdev_iomap_begin
Date: Fri, 03 May 2024 09:05:54 -0600 [thread overview]
Message-ID: <171474875400.33279.6512906060593711937.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240503081042.2078062-1-hch@lst.de>
On Fri, 03 May 2024 10:10:42 +0200, Christoph Hellwig wrote:
> blkdev_iomap_begin rounds down the offset to the logical block size
> before stashing it in iomap->offset and checking that it still is
> inside the inode size.
>
> Check the i_size check to the raw pos value so that we don't try a
> zero size write if iter->pos is unaligned.
>
> [...]
Applied, thanks!
[1/1] block: refine the EOF check in blkdev_iomap_begin
commit: 0c12028aec837f5a002009bbf68d179d506510e8
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-05-03 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 8:10 [PATCH] block: refine the EOF check in blkdev_iomap_begin Christoph Hellwig
2024-05-03 15:05 ` Jens Axboe [this message]
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=171474875400.33279.6512906060593711937.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=syzbot+0a3683a0a6fecf909244@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 read-only IMAP folder(s) and NNTP newsgroup(s).