From: Jens Axboe <axboe@kernel.dk>
To: Johannes Thumshirn <johannes.thumshirn@wdc.com>
Cc: linux-block@vger.kernel.org, Christoph Hellwig <hch@lst.de>,
Damien Le Moal <dlemoal@kernel.org>
Subject: Re: [PATCH] zloop: print device that had errors
Date: Fri, 16 Oct 2026 08:44:13 -0600 [thread overview]
Message-ID: <5ce34052-c18b-4e3a-ab3e-f689218f6208@kernel.dk> (raw)
In-Reply-To: <237f8537-79cc-4ac0-83ae-31ea0d51e0b9@wdc.com>
On 10/16/26 8:40 AM, Johannes Thumshirn wrote:
> On 16.10.26 16:23, Jens Axboe wrote:
>> On 10/16/26 1:30 AM, Johannes Thumshirn wrote:
>>> When testing zoned filesystems that span multiple zloop drives it can be
>>> difficult to figure out which devices access caused an error.
>>>
>>> Prefix the error messages where we have the disk available with the disk
>>> name.
>>
>> I don't know what this is against (doesn't say), and it doesn't apply to
>> the next branch...
>>
>
> Strange, it applied on 34fbfb9d8d1f ("Merge branch 'for-7.4/block' into for-next") in your tree.
Does it apply to for-7.4/block? That's what I used. Doing other git work
right now and will re-check later.
--
Jens Axboe
next prev parent reply other threads:[~2026-10-16 14:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 7:30 [PATCH] zloop: print device that had errors Johannes Thumshirn
2026-10-16 7:48 ` Christoph Hellwig
2026-10-16 14:23 ` Jens Axboe
2026-10-16 14:40 ` Johannes Thumshirn
2026-10-16 14:44 ` Jens Axboe [this message]
2026-10-16 15:00 ` Johannes Thumshirn
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=5ce34052-c18b-4e3a-ab3e-f689218f6208@kernel.dk \
--to=axboe@kernel.dk \
--cc=dlemoal@kernel.org \
--cc=hch@lst.de \
--cc=johannes.thumshirn@wdc.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox