From: Hannes Reinecke <hare@suse.de>
To: Tal Zussman <tz2294@columbia.edu>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>,
Johannes Thumshirn <johannes.thumshirn@wdc.com>,
Luis Chamberlain <mcgrof@kernel.org>,
Hannes Reinecke <hare@kernel.org>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
John Garry <john.garry@linux.dev>,
Christian Brauner <brauner@kernel.org>,
"Darrick J. Wong" <djwong@kernel.org>,
Keith Busch <kbusch@kernel.org>,
"Martin K. Petersen" <mkp@kernel.org>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
Sashiko <sashiko-bot@kernel.org>
Subject: Re: [PATCH v4 5/8] block: fail a short atomic pin in bio_iov_iter_get_pages()
Date: Tue, 22 Sep 2026 07:40:42 +0200 [thread overview]
Message-ID: <341ec217-4b3b-49aa-9481-4cf7e8952228@suse.de> (raw)
In-Reply-To: <20260921-blkdev-fixes-v4-5-e2801f71ede9@columbia.edu>
On 9/22/26 4:54 AM, Tal Zussman wrote:
> On a partial page pin, __blkdev_direct_IO_simple() and
> __blkdev_direct_IO_async() submit what was pinned with REQ_ATOMIC set
> and leave the rest to the buffered fallback, tearing an IOCB_ATOMIC
> write.
>
> This can be triggered deterministically. A 16K pwritev2(RWF_ATOMIC)
> whose last page is PROT_NONE, on a scsi_debug device with atomic_wr=1,
> completes short with only three of the four pages written, violating
> RWF_ATOMIC semantics.
>
> Make bio_iov_iter_get_pages() release the pins and return -EINVAL when
> a REQ_ATOMIC bio doesn't cover the whole iterator, since an atomic
> write is submitted as a single bio and a short one would be torn. That
> covers iomap as well, where a partially unmapped buffer could trip the
> WARN_ON_ONCE() in iomap_dio_bio_iter_one(). The async block device path
> currently sets REQ_ATOMIC after pinning, so set it before, and move
> REQ_NOWAIT along with it.
>
> Fixes: caf336f81b3a ("block: Add fops atomic write support")
> Reported-by: Sashiko <sashiko-bot@kernel.org>
> Link: https://sashiko.dev/#/patchset/20260802-blkdev-fixes-v1-0-a82fc549fd74%40columbia.edu?part=2
> Assisted-by: Claude:claude-fable-5
> Signed-off-by: Tal Zussman <tz2294@columbia.edu>
> ---
> block/bio.c | 29 ++++++++++++++++++++++-------
> block/fops.c | 12 ++++++------
> 2 files changed, 28 insertions(+), 13 deletions(-)
>
> diff --git a/block/bio.c b/block/bio.c
> index f95b63c0604a..14429a5d4e68 100644
> --- a/block/bio.c
> +++ b/block/bio.c
> @@ -1285,6 +1285,7 @@ int bio_iov_iter_get_pages(struct bio *bio, struct iov_iter *iter,
> unsigned mem_align_mask, unsigned len_align_mask)
> {
> iov_iter_extraction_t flags = 0;
> + int ret;
>
> if (WARN_ON_ONCE(bio_flagged(bio, BIO_CLONED)))
> return -EIO;
> @@ -1304,34 +1305,48 @@ int bio_iov_iter_get_pages(struct bio *bio, struct iov_iter *iter,
> flags |= ITER_ALLOW_P2PDMA;
>
> do {
> - ssize_t ret;
> + ssize_t size;
>
> - ret = iov_iter_extract_bvecs(iter, bio->bi_io_vec,
> + size = iov_iter_extract_bvecs(iter, bio->bi_io_vec,
> BIO_MAX_SIZE - bio->bi_iter.bi_size,
> &bio->bi_vcnt, bio->bi_max_vecs,
> mem_align_mask, flags);
> - if (ret <= 0) {
> + if (size <= 0) {
> /*
> * A misaligned vector fails the whole I/O. Release any
> * pages pinned by earlier iterations before returning
> * since this bio won't be submitted to release them.
> */
> - if (ret == -EINVAL) {
> + if (size == -EINVAL) {
> bio_release_pages(bio, false);
> bio_clear_flag(bio, BIO_PAGE_PINNED);
> bio->bi_vcnt = 0;
> }
> if (!bio->bi_vcnt)
> - return ret;
> + return size;
> break;
> }
> - bio->bi_iter.bi_size += ret;
> + bio->bi_iter.bi_size += size;
> } while (iov_iter_count(iter) && !bio_full(bio, 0));
>
I would swizzle the use of 'ret' and 'size' here; leaving 'ret'
untouched and use 'size' as the new variable. That will reduce
code churn and makes the patch easier to read.
> if (is_pci_p2pdma_page(bio->bi_io_vec->bv_page))
> bio->bi_opf |= REQ_NOMERGE;
> - return bio_iov_iter_align_down(bio, iter,
> + ret = bio_iov_iter_align_down(bio, iter,
> &bio->bi_io_vec[bio->bi_vcnt - 1], len_align_mask);
> + if (ret)
> + return ret;
> +
> + /*
> + * An atomic write is submitted as a single bio, so it has to cover
> + * the whole iterator or it would be torn.
> + */
> + if ((bio->bi_opf & REQ_ATOMIC) && iov_iter_count(iter)) {
> + bio_release_pages(bio, false);
> + bio_clear_flag(bio, BIO_PAGE_PINNED);
> + bio->bi_vcnt = 0;
> + return -EINVAL;
> + }
> + return 0;
> }
>
> static struct folio *folio_alloc_greedy(gfp_t gfp, size_t *size,
> diff --git a/block/fops.c b/block/fops.c
> index a3a709697b40..90777e8a9a6c 100644
> --- a/block/fops.c
> +++ b/block/fops.c
> @@ -342,6 +342,12 @@ static ssize_t __blkdev_direct_IO_async(struct kiocb *iocb,
> bio->bi_end_io = blkdev_bio_end_io_async;
> bio->bi_ioprio = iocb->ki_ioprio;
>
> + if (iocb->ki_flags & IOCB_ATOMIC)
> + bio->bi_opf |= REQ_ATOMIC;
> +
> + if (iocb->ki_flags & IOCB_NOWAIT)
> + bio->bi_opf |= REQ_NOWAIT;
> +
> /*
> * Users don't rely on the iterator being in any particular
> * state for async I/O returning -EIOCBQUEUED, hence we can
> @@ -371,12 +377,6 @@ static ssize_t __blkdev_direct_IO_async(struct kiocb *iocb,
> goto out_bio_put;
> }
>
> - if (iocb->ki_flags & IOCB_ATOMIC)
> - bio->bi_opf |= REQ_ATOMIC;
> -
> - if (iocb->ki_flags & IOCB_NOWAIT)
> - bio->bi_opf |= REQ_NOWAIT;
> -
> if (iocb->ki_flags & IOCB_HIPRI) {
> bio->bi_opf |= REQ_POLLED;
> submit_bio(bio);
>
Otherwise looks good.
Cheers,
Hannes
--
Dr. Hannes Reinecke Kernel Storage Architect
hare@suse.de +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich
next prev parent reply other threads:[~2026-09-22 5:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 2:53 [PATCH v4 0/8] block device fixes for large block sizes, IOCB_NOWAIT, and direct I/O Tal Zussman
2026-09-22 2:53 ` [PATCH v4 1/8] block: use iomap_dirty_folio for block devices Tal Zussman
2026-09-22 2:53 ` [PATCH v4 2/8] block: take i_rwsem for the direct I/O write fallback Tal Zussman
2026-09-22 2:54 ` [PATCH v4 3/8] block: take i_rwsem for the splice read path Tal Zussman
2026-09-22 2:54 ` [PATCH v4 4/8] block: honor IOCB_NOWAIT in the block device buffered " Tal Zussman
2026-09-22 2:54 ` [PATCH v4 5/8] block: fail a short atomic pin in bio_iov_iter_get_pages() Tal Zussman
2026-09-22 5:40 ` Hannes Reinecke [this message]
2026-09-23 23:37 ` Tal Zussman
2026-09-22 10:16 ` John Garry
2026-09-23 23:38 ` Tal Zussman
2026-09-22 2:54 ` [PATCH v4 6/8] block: don't fall back to buffered I/O for atomic writes Tal Zussman
2026-09-22 5:41 ` Hannes Reinecke
2026-09-22 10:05 ` John Garry
2026-09-23 23:39 ` Tal Zussman
2026-09-22 2:54 ` [PATCH v4 7/8] block: unpin all pages of a bvec in bio_iov_iter_align_down() Tal Zussman
2026-09-22 13:09 ` Christoph Hellwig
2026-09-22 2:54 ` [PATCH v4 8/8] block: remove dead metadata handling from the async direct I/O path Tal Zussman
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=341ec217-4b3b-49aa-9481-4cf7e8952228@suse.de \
--to=hare@suse.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=djwong@kernel.org \
--cc=hare@kernel.org \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--cc=john.garry@linux.dev \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=mkp@kernel.org \
--cc=sashiko-bot@kernel.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=tz2294@columbia.edu \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®