From: Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Andreas Gruenbacher <agruenba@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"drbd-dev@lists.linbit.com" <drbd-dev@lists.linbit.com>,
"linux-bcache@vger.kernel.org" <linux-bcache@vger.kernel.org>,
"dm-devel@lists.linux.dev" <dm-devel@lists.linux.dev>,
"linux-f2fs-devel@lists.sourceforge.net"
<linux-f2fs-devel@lists.sourceforge.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] simple bio cleanups
Date: Fri, 13 Mar 2026 12:53:43 +0000 [thread overview]
Message-ID: <abQHNzJ0FR1EF0NX@shinmob> (raw)
In-Reply-To: <20260304190424.291743-1-agruenba@redhat.com>
On Mar 04, 2026 / 20:04, Andreas Gruenbacher wrote:
> Jens,
>
> here are some simple bio related cleanups. Any thoughts? Can those go
> in via your tree?
>
> Thanks,
> Andreas
>
> Andreas Gruenbacher (4):
> block: consecutive blk_status_t error codes
> block: get rid of blk_status_to_{errno,str} inconsistency
> bio: rename bio_chain arguments
> bio: use bio_io_error more often
Hello Andreas, during blktests CI trial runs, I noticed that this patch series
triggered failures of three blktests test cases: scsi/004, scsi/007 and
throtl/004. Do you see which patch triggered these failures?
scsi/004 (ensure repeated TASK SET FULL results in EIO on timing out command) [failed]
runtime ... 3.855s
--- tests/scsi/004.out 2026-03-12 15:23:54.664435639 +0000
+++ /home/fedora/blktests/results/nodev/scsi/004.out.bad 2026-03-12 18:13:40.059747989 +0000
@@ -1,3 +1,2 @@
Running scsi/004
-Input/output error
Test complete
scsi/007 (Trigger the SCSI error handler) [failed]
runtime ... 115.385s
--- tests/scsi/007.out 2026-03-12 15:23:54.668435644 +0000
+++ /home/fedora/blktests/results/nodev/scsi/007.out.bad 2026-03-12 18:15:55.054944537 +0000
@@ -1,3 +1,3 @@
Running scsi/007
-Reading from scsi_debug failed
+Reading from scsi_debug succeeded
Test complete
throtl/004 (nullb) (delete disk while IO is throttled) [failed]
runtime ... 1.643s
--- tests/throtl/004.out 2026-03-12 15:23:54.710435695 +0000
+++ /home/fedora/blktests/results/nodev_nullb/throtl/004.out.bad 2026-03-12 18:20:46.314368581 +0000
@@ -1,3 +1,2 @@
Running throtl/004
-Input/output error
Test complete
next prev parent reply other threads:[~2026-03-13 12:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 19:04 [PATCH 0/4] simple bio cleanups Andreas Gruenbacher
2026-03-04 19:04 ` [PATCH 1/4] block: consecutive blk_status_t error codes Andreas Gruenbacher
2026-03-05 14:12 ` Christoph Hellwig
2026-03-05 22:36 ` John Garry
2026-03-04 19:04 ` [PATCH 2/4] block: get rid of blk_status_to_{errno,str} inconsistency Andreas Gruenbacher
2026-03-05 14:13 ` Christoph Hellwig
2026-03-06 15:51 ` John Garry
2026-03-04 19:04 ` [PATCH 3/4] bio: rename bio_chain arguments Andreas Gruenbacher
2026-03-04 19:04 ` [PATCH 4/4] bio: use bio_io_error more often Andreas Gruenbacher
2026-03-05 14:14 ` Christoph Hellwig
2026-03-05 18:37 ` Andreas Gruenbacher
2026-03-05 14:32 ` Coly Li
2026-03-13 12:53 ` Shinichiro Kawasaki [this message]
2026-03-13 14:35 ` [PATCH 0/4] simple bio cleanups Andreas Gruenbacher
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=abQHNzJ0FR1EF0NX@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=agruenba@redhat.com \
--cc=axboe@kernel.dk \
--cc=dm-devel@lists.linux.dev \
--cc=drbd-dev@lists.linbit.com \
--cc=linux-bcache@vger.kernel.org \
--cc=linux-block@vger.kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox