From: Damien Le Moal <dlemoal@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jens Axboe <axboe@kernel.dk>
Cc: linux-block@vger.kernel.org
Subject: Re: [PATCH 2/2] zloop: check for spurious options passed to remove
Date: Wed, 25 Feb 2026 05:29:07 +0900 [thread overview]
Message-ID: <75f48cfb-b426-458d-8f26-17d6de2f2a2b@kernel.org> (raw)
In-Reply-To: <20260224142153.368472-3-hch@lst.de>
On 2/24/26 23:21, Christoph Hellwig wrote:
> Zloop uses a command option parser for all control commands,
> but most options are only valid for adding a new device. Check
> for incorrectly specified options in the remove handler.
>
> Fixes: eb0570c7df23 ("block: new zoned loop block device driver")
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Damien Le Moal <dlemoal@kernel.org>
--
Damien Le Moal
Western Digital Research
next prev parent reply other threads:[~2026-02-24 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-24 14:21 zloop fixes Christoph Hellwig
2026-02-24 14:21 ` [PATCH 1/2] zloop: advertise a volatile write cache Christoph Hellwig
2026-02-24 20:28 ` Damien Le Moal
2026-02-24 21:50 ` Jens Axboe
2026-02-24 14:21 ` [PATCH 2/2] zloop: check for spurious options passed to remove Christoph Hellwig
2026-02-24 20:29 ` Damien Le Moal [this message]
2026-02-24 21:18 ` zloop fixes Martin K. Petersen
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=75f48cfb-b426-458d-8f26-17d6de2f2a2b@kernel.org \
--to=dlemoal@kernel.org \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--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