From: Hongbo Li <lihongbo22@huawei.com>
To: <viro@zeniv.linux.org.uk>, <brauner@kernel.org>, <jack@suse.cz>,
<tytso@mit.edu>, <adilger.kernel@dilger.ca>
Cc: <lczerner@redhat.com>, <cmaiolino@redhat.com>,
<linux-fsdevel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<yi.zhang@huawei.com>, <lihongbo22@huawei.com>
Subject: [PATCH v2 0/4] enhance the path resolution capability in fs_parser
Date: Mon, 27 May 2024 15:58:50 +0800 [thread overview]
Message-ID: <20240527075854.1260981-1-lihongbo22@huawei.com> (raw)
Mount options with path should be parsed into block device or inode. As
the new mount API provides a serial of parsers, path should also be
looked up into block device within these parsers, not in each specific
filesystem.
The following is a brief overview of the patches, see the patches for
more details.
Patch 1-2: Enhance the path resolution capability in fs_parser.
Patch 3: Fix the `journal_path` options error in ext4.
Patch 4: Remove the `fs_lookup_param` and its description.
Comments and questions are, as always, welcome.
Thanks,
Hongbo
Changes since v1:
* Fix test robot warning and rebase on latest code.
Hongbo Li (4):
fs: add blockdev parser for filesystem mount option.
fs: add path parser for filesystem mount option.
fs: ext4: support relative path for `journal_path` in mount option.
fs: remove fs_lookup_param and its description.
Documentation/filesystems/mount_api.rst | 17 +---
fs/ext4/super.c | 26 +----
fs/fs_parser.c | 125 +++++++++++++-----------
include/linux/fs_parser.h | 7 +-
4 files changed, 71 insertions(+), 104 deletions(-)
--
2.34.1
next reply other threads:[~2024-05-27 7:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-27 7:58 Hongbo Li [this message]
2024-05-27 7:58 ` [PATCH v2 1/4] fs: add blockdev parser for filesystem mount option Hongbo Li
2024-05-27 7:58 ` [PATCH v2 2/4] fs: add path " Hongbo Li
2024-05-27 14:32 ` Christian Brauner
2024-05-27 16:26 ` Christoph Hellwig
2024-05-27 7:58 ` [PATCH v2 3/4] fs: ext4: support relative path for `journal_path` in " Hongbo Li
2024-05-27 15:39 ` Christian Brauner
2024-05-27 7:58 ` [PATCH v2 4/4] fs: remove fs_lookup_param and its description Hongbo Li
2024-05-27 15:08 ` [PATCH v2 0/4] enhance the path resolution capability in fs_parser 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=20240527075854.1260981-1-lihongbo22@huawei.com \
--to=lihongbo22@huawei.com \
--cc=adilger.kernel@dilger.ca \
--cc=brauner@kernel.org \
--cc=cmaiolino@redhat.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=viro@zeniv.linux.org.uk \
--cc=yi.zhang@huawei.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