From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: Damien Le Moal <dlemoal@kernel.org>
Cc: linux-block@vger.kernel.org, blktests-ci-bot@kernel.org
Subject: Re: [PATCH v7 00/10] Add support for storage element depopulation
Date: Mon, 19 Oct 2026 20:01:36 +0900 [thread overview]
Message-ID: <atX3_T-5osUcVDPh@shinmob> (raw)
In-Reply-To: <286f96be-9ddd-4378-a28f-67d736237f64@kernel.org>
On Oct 19, 2026 / 12:41, Damien Le Moal wrote:
> On 2026/10/14 9:18, shinichiro.kawasaki@wdc.com wrote:
> > Dear patch submitter,
> >
> > Blktests CI has tested the following submission:
> > Status: FAILURE
> > Name: [v7,00/10] Add support for storage element depopulation
> > Patchwork: https://patchwork.kernel.org/series/1185265/&state=*
> > Run record: https://github.com/linux-blktests/linux-block/actions/runs/38517856454
> >
> >
> > Failed test cases: loop/006
>
> I tracked the failure to:
>
> ioctl(ctl, LOOP_CTL_GET_FREE)
>
> failing in util-linux losetup lib.
> No idea why. Running losetup -f works.
>
> Note that I see the failure in block/for-next too without my patches, so this
> seems unrelated to my patch series.
Sorry for this false-positive report. I believe the failure cause is another
change in the loop driver "loop: remove support for swapping loop fds" [*].
[*] https://lore.kernel.org/linux-block/as8-8rDJmUb1FxbP@shinmob/
I have disabled loop/006 for the future blktests CI runs, so I expect no more
failure report for loop/006.
prev parent reply other threads:[~2026-10-19 11:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 5:33 [PATCH v7 00/10] Add support for storage element depopulation Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 01/10] block: introduce disk_zone_is_offline() Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 02/10] block: refactor blk_revalidate_disk_zones() Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 03/10] block: introduce storage element management Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 04/10] block: add storage element management ioctls Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 05/10] zloop: avoid potential wp_lock deadlocks Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 06/10] zloop: add storage element emulation Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 07/10] zloop: add degrade_element control command Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 08/10] scsi: sd: fail read commands to offline zones early Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 09/10] scsi: sd_zbc: always revalidate zones for disks supporting head depopulation Damien Le Moal
2026-10-14 5:33 ` [PATCH v7 10/10] scsi: sd_zbc: define storage element management operations Damien Le Moal
2026-10-14 7:18 ` [PATCH v7 00/10] Add support for storage element depopulation shinichiro.kawasaki
2026-10-19 10:41 ` Damien Le Moal
2026-10-19 11:01 ` 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=atX3_T-5osUcVDPh@shinmob \
--to=shinichiro.kawasaki@wdc.com \
--cc=blktests-ci-bot@kernel.org \
--cc=dlemoal@kernel.org \
--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