From: David Sterba <dsterba@suse.cz>
To: Daniel Xu <dxu@dxuuu.xyz>
Cc: linux-btrfs@vger.kernel.org, dsterba@suse.cz, kernel-team@fb.com
Subject: Re: [PATCH 0/3] btrfs-progs: rescue: Add create-control-device subcommand
Date: Fri, 19 Feb 2021 15:48:17 +0100 [thread overview]
Message-ID: <20210219144817.GD1993@twin.jikos.cz> (raw)
In-Reply-To: <cover.1604013169.git.dxu@dxuuu.xyz>
On Thu, Oct 29, 2020 at 04:17:35PM -0700, Daniel Xu wrote:
> This patchset adds a new `btrfs rescue create-control-device` subcommand
> that acts as a convenient way to invoke:
>
> # mknod --mode=600 c 10 234 /dev/btrfs-control
>
> on systems that don't have `mknod` installed or when you're lazy.
Well, I don't think the part 'lazy' applies.
The whole thing with the control device is simpler that I originally
thought. On a system without loaded btrfs module there's no
/dev/btrfs-control. This is correct because the device node is created
at load time or when btrfs_interface_init is called.
Creating just the device node makes no sense because there's nothing
handling it. Once module is loaded it appears and works as expected.
The only case where the rescue command makes sense is when the module is
loaded, device node creatd and then manually deleted. This is possible
but highly unlikely. For that reason the rescue command still has some
sense but the reasoning needs to reflect how it's related to the module
status.
As this is docs update only, I'll fix that myself, no need to resend.
prev parent reply other threads:[~2021-02-19 14:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 23:17 [PATCH 0/3] btrfs-progs: rescue: Add create-control-device subcommand Daniel Xu
2020-10-29 23:17 ` [PATCH 1/3] " Daniel Xu
2020-11-11 1:33 ` Daniel Xu
2020-10-29 23:17 ` [PATCH 2/3] btrfs-progs: bash: Update completion script with create-control-device Daniel Xu
2020-10-29 23:17 ` [PATCH 3/3] btrfs-progs: rescue: Update docs " Daniel Xu
2020-11-13 20:34 ` [PATCH 0/3] btrfs-progs: rescue: Add create-control-device subcommand Josef Bacik
2021-02-19 14:48 ` 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=20210219144817.GD1993@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dxu@dxuuu.xyz \
--cc=kernel-team@fb.com \
--cc=linux-btrfs@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