From: Al Viro <viro@zeniv.linux.org.uk>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/4] fs: remove the unused fs_lookup_param function
Date: Sat, 26 Sep 2020 15:57:07 +0100 [thread overview]
Message-ID: <20200926145707.GA3421308@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20200926092051.115577-2-hch@lst.de>
On Sat, Sep 26, 2020 at 11:20:48AM +0200, Christoph Hellwig wrote:
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> Documentation/filesystems/mount_api.rst | 18 +-------
> fs/fs_parser.c | 56 -------------------------
> include/linux/fs_parser.h | 5 ---
> 3 files changed, 2 insertions(+), 77 deletions(-)
>
> diff --git a/Documentation/filesystems/mount_api.rst b/Documentation/filesystems/mount_api.rst
> index 29c169c68961f3..dbff847986da47 100644
> --- a/Documentation/filesystems/mount_api.rst
> +++ b/Documentation/filesystems/mount_api.rst
> @@ -254,8 +254,8 @@ manage the filesystem context. They are as follows:
> will have been weeded out and fc->sb_flags updated in the context.
> Security options will also have been weeded out and fc->security updated.
>
> - The parameter can be parsed with fs_parse() and fs_lookup_param(). Note
> - that the source(s) are presented as parameters named "source".
> + The parameter can be parsed with fs_parse(). Note that the source(s) are
> + presented as parameters named "source".
Umm... Not sure - I'm not too fond of fs_lookup_param(), but AFAIK there are
efforts to convert more filesystems to new mount API and I don't know if any
of those are currently using it - this work has moved to individual fs trees
now, so it's hard to keep track of.
Generally I would say "if it's out of tree, it's not our problem", but the new
API is fairly recent and conversions of in-tree filesystems aree still in
progress. And they are likely to stay in topical branches in the regular
git trees of those in-tree filesystems while they are being developed, so
right now I would rather be careful with removals in that area, short of
serious problem with the primitive itself. Being able to make lookup_filename()
static is obviously nice, but considering the changes done later in the series...
Let's hold it back for now.
next prev parent reply other threads:[~2020-09-26 14:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 9:20 small pathname lookup cleanups Christoph Hellwig
2020-09-26 9:20 ` [PATCH 1/4] fs: remove the unused fs_lookup_param function Christoph Hellwig
2020-09-26 14:57 ` Al Viro [this message]
2020-09-26 9:20 ` [PATCH 2/4] fs: mark filename_lookup static Christoph Hellwig
2020-09-26 9:20 ` [PATCH 3/4] fs: pass a nameidata into filename_lookup Christoph Hellwig
2020-09-26 14:49 ` Al Viro
2020-09-26 9:20 ` [PATCH 4/4] fs: simplify vfs_path_lookup Christoph Hellwig
2020-09-26 14:46 ` Al Viro
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=20200926145707.GA3421308@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=hch@lst.de \
--cc=linux-fsdevel@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;
as well as URLs for NNTP newsgroup(s).