From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 3/4] fs: remove fsparam_path / fs_param_is_path
Date: Thu, 19 Feb 2026 08:04:28 -0800 [thread overview]
Message-ID: <20260219160428.GQ6467@frogsfrogsfrogs> (raw)
In-Reply-To: <20260219065014.3550402-4-hch@lst.de>
On Thu, Feb 19, 2026 at 07:50:03AM +0100, Christoph Hellwig wrote:
> These are not used anywhere even after the fs_context conversion is
> finished, so remove them.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> Documentation/filesystems/mount_api.rst | 2 --
> fs/fs_parser.c | 7 -------
> include/linux/fs_parser.h | 3 +--
> 3 files changed, 1 insertion(+), 11 deletions(-)
>
> diff --git a/Documentation/filesystems/mount_api.rst b/Documentation/filesystems/mount_api.rst
> index b4a0f23914a6..e8b94357b4df 100644
> --- a/Documentation/filesystems/mount_api.rst
> +++ b/Documentation/filesystems/mount_api.rst
> @@ -648,7 +648,6 @@ The members are as follows:
> fs_param_is_enum Enum value name result->uint_32
> fs_param_is_string Arbitrary string param->string
> fs_param_is_blockdev Blockdev path * Needs lookup
Unrelated: should xfs be using fsparam_bdev for its logdev/rtdev mount
options?
Or, more crazily, should it grow logfd/rtfd options that use fsparam_fd?
This patch looks ok,
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>
--D
> - fs_param_is_path Path * Needs lookup
> fs_param_is_fd File descriptor result->int_32
> fs_param_is_uid User ID (u32) result->uid
> fs_param_is_gid Group ID (u32) result->gid
> @@ -681,7 +680,6 @@ The members are as follows:
> fsparam_enum() fs_param_is_enum
> fsparam_string() fs_param_is_string
> fsparam_bdev() fs_param_is_blockdev
> - fsparam_path() fs_param_is_path
> fsparam_fd() fs_param_is_fd
> fsparam_uid() fs_param_is_uid
> fsparam_gid() fs_param_is_gid
> diff --git a/fs/fs_parser.c b/fs/fs_parser.c
> index 79e8fe9176fa..b4cc4cce518a 100644
> --- a/fs/fs_parser.c
> +++ b/fs/fs_parser.c
> @@ -361,13 +361,6 @@ int fs_param_is_blockdev(struct p_log *log, const struct fs_parameter_spec *p,
> }
> EXPORT_SYMBOL(fs_param_is_blockdev);
>
> -int fs_param_is_path(struct p_log *log, const struct fs_parameter_spec *p,
> - struct fs_parameter *param, struct fs_parse_result *result)
> -{
> - return 0;
> -}
> -EXPORT_SYMBOL(fs_param_is_path);
> -
> #ifdef CONFIG_VALIDATE_FS_PARSER
> /**
> * fs_validate_description - Validate a parameter specification array
> diff --git a/include/linux/fs_parser.h b/include/linux/fs_parser.h
> index 961562b101c5..98b83708f92b 100644
> --- a/include/linux/fs_parser.h
> +++ b/include/linux/fs_parser.h
> @@ -28,7 +28,7 @@ typedef int fs_param_type(struct p_log *,
> */
> fs_param_type fs_param_is_bool, fs_param_is_u32, fs_param_is_s32, fs_param_is_u64,
> fs_param_is_enum, fs_param_is_string, fs_param_is_blockdev,
> - fs_param_is_path, fs_param_is_fd, fs_param_is_uid, fs_param_is_gid,
> + fs_param_is_fd, fs_param_is_uid, fs_param_is_gid,
> fs_param_is_file_or_string;
>
> /*
> @@ -126,7 +126,6 @@ static inline bool fs_validate_description(const char *name,
> #define fsparam_string(NAME, OPT) \
> __fsparam(fs_param_is_string, NAME, OPT, 0, NULL)
> #define fsparam_bdev(NAME, OPT) __fsparam(fs_param_is_blockdev, NAME, OPT, 0, NULL)
> -#define fsparam_path(NAME, OPT) __fsparam(fs_param_is_path, NAME, OPT, 0, NULL)
> #define fsparam_fd(NAME, OPT) __fsparam(fs_param_is_fd, NAME, OPT, 0, NULL)
> #define fsparam_file_or_string(NAME, OPT) \
> __fsparam(fs_param_is_file_or_string, NAME, OPT, 0, NULL)
> --
> 2.47.3
>
>
next prev parent reply other threads:[~2026-02-19 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-19 6:50 remove or unexport unused fs_conext infrastructure Christoph Hellwig
2026-02-19 6:50 ` [PATCH 1/4] fs: mark bool_names static Christoph Hellwig
2026-02-19 6:50 ` [PATCH 2/4] fs: remove fsparam_blob / fs_param_is_blob Christoph Hellwig
2026-02-19 6:50 ` [PATCH 3/4] fs: remove fsparam_path / fs_param_is_path Christoph Hellwig
2026-02-19 16:04 ` Darrick J. Wong [this message]
2026-02-20 15:24 ` Christoph Hellwig
2026-02-20 18:21 ` Darrick J. Wong
2026-02-19 6:50 ` [PATCH 4/4] fs: unexport fs_context_for_reconfigure Christoph Hellwig
2026-02-19 11:45 ` remove or unexport unused fs_conext infrastructure Jan Kara
2026-02-19 13:35 ` Christian Brauner
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=20260219160428.GQ6467@frogsfrogsfrogs \
--to=djwong@kernel.org \
--cc=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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