From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: enable shutdown ioctl for non-experimental builds
Date: Tue, 14 Apr 2026 04:45:41 +0200 [thread overview]
Message-ID: <20260414024541.GM12792@twin.jikos.cz> (raw)
In-Reply-To: <f818123ba52a15913ea862aba75eacdbf4c06aeb.1776133240.git.wqu@suse.com>
On Tue, Apr 14, 2026 at 11:51:15AM +0930, Qu Wenruo wrote:
> Although commit 304076527c38 ("btrfs: move shutdown and remove_bdev
> callbacks out of experimental features") tries to move both shutdown and
> remove_bdev out of experimental features, that commit has only addressed
> the super block operation callback, the ioctl one is left untouched.
>
> Fix that missing aspect by also moving shutdown ioctl out of
> experimental features.
>
> Since we're here, also add unknown flag detection to reject any
> unsupported shutdown flags.
>
> Fixes: 304076527c38 ("btrfs: move shutdown and remove_bdev callbacks out of experimental features")
> Signed-off-by: Qu Wenruo <wqu@suse.com>
Reviewed-by: David Sterba <dsterba@suse.com>
prev parent reply other threads:[~2026-04-14 2:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 2:21 [PATCH] btrfs: enable shutdown ioctl for non-experimental builds Qu Wenruo
2026-04-14 2:45 ` David Sterba [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=20260414024541.GM12792@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@suse.com \
/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