All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: 0wnerD1ed <l7z@0b1t.tech>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH blktests] block/046: skip with the new XFS read-bounce implementation
Date: Fri, 25 Sep 2026 14:31:27 +0900	[thread overview]
Message-ID: <arYG96raJ0gESSo-@shinmob> (raw)
In-Reply-To: <CAKTh27_iPvKWV8_bLMwwhEZAD+XPXimBdpz4D8iuue8mSh2A=g@mail.gmail.com>

On Sep 21, 2026 / 16:58, 0wnerD1ed wrote:
> block/046 uses a deliberately misaligned one-byte iovec to exercise the
> special bvec layout in bio_iov_iter_bounce_read().
> 
> The new XFS lazy read-bounce implementation no longer sets
> IOMAP_DIO_BOUNCE before extracting the user pages.  The ordinary path now
> rejects that iovec with EINVAL, and a later patch removes the legacy helper
> entirely.
> 
> Detect the per-mount csum/read_bounce interface and mark the test not run
> after cleaning up the XFS mount and null_blk device.  This retains the
> regression coverage on older kernels without treating the expected EINVAL
> as a successful result.
> 
> Reported-by: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
> Link: https://lore.kernel.org/r/arDN1UdZIydNLUjz@shinmob
> Link: https://lore.kernel.org/r/20260921082240.GA19833@lst.de
> Signed-off-by: 0wnerD1ed <l7z@0b1t.tech>

I applied this patch. Thank you for the swift fix!

      parent reply	other threads:[~2026-09-25  5:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21  8:58 [PATCH blktests] block/046: skip with the new XFS read-bounce implementation 0wnerD1ed
2026-09-21  9:12 ` 0wnerD1ed
2026-09-22 13:21   ` Christoph Hellwig
2026-09-25  5:31 ` Shin'ichiro Kawasaki [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=arYG96raJ0gESSo-@shinmob \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=hch@lst.de \
    --cc=l7z@0b1t.tech \
    --cc=linux-block@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.