All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>
To: linux-block@vger.kernel.org
Cc: blktests-ci-bot@kernel.org, Jens Axboe <axboe@kernel.dk>,
	 Jan Kara <jack@suse.cz>, Christian Brauner <brauner@kernel.org>
Subject: Re: [PATCH] loop: remove support for swapping loop fds
Date: Wed, 14 Oct 2026 17:47:48 +0900	[thread overview]
Message-ID: <as8-8rDJmUb1FxbP@shinmob> (raw)
In-Reply-To: <49a2d2f1d44a018dbe2a3da155b5fedea30cf98ea484bdc19da2f9cf97c4e0da@mailrelay.wdc.com>

On Oct 13, 2026 / 16:03, shinichiro.kawasaki@wdc.com wrote:
> Dear patch submitter,
> 
> Blktests CI has tested the following submission:
> Status:     FAILURE
> Name:       loop: remove support for swapping loop fds

This kernel patch removed the support of ioctl LOOP_CHANGE_FD.

> Patchwork:  https://patchwork.kernel.org/series/1183887/&state=*
> Run record: https://github.com/linux-blktests/linux-block/actions/runs/38278109458
> 
> 
> Failed test cases: loop/006

And this test case confirms that the ioctl LOOP_CHANGE_FD works well. After
removing the ioctl, the test case failure is expected. Blktests CI caught it,
and reported it with this e-mail.

The test case loop/006 is no longer valid, and its failure should be handled.
I can think of two action candidates:

  1) just remove the test case loop/006
  2) skip the test case for kernel versions larger than v7.4, and keep it for
     older kernel versions

The ioctl has been broken for certain period, so I think action 1) is more
appropriate. If anyone has different opinion, please share. Otherwise, I will
post a patch to remove loop/006.

      reply	other threads:[~2026-10-14  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 12:47 [PATCH] loop: remove support for swapping loop fds Christian Brauner
2026-10-12 16:19 ` Jan Kara
2026-10-12 18:51 ` Jens Axboe
2026-10-13 23:03 ` shinichiro.kawasaki
2026-10-14  8:47   ` 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=as8-8rDJmUb1FxbP@shinmob \
    --to=shinichiro.kawasaki@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=blktests-ci-bot@kernel.org \
    --cc=brauner@kernel.org \
    --cc=jack@suse.cz \
    --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.