From: Eric Sandeen <sandeen@redhat.com>
To: Bill O'Donnell <bodonnel@redhat.com>, linux-fsdevel@vger.kernel.org
Cc: brauner@kernel.org
Subject: Re: [PATCH] minix: convert minix to use the new mount api
Date: Tue, 5 Mar 2024 15:27:17 -0600 [thread overview]
Message-ID: <c4a2e820-70e5-453c-b022-a3207fb9119d@redhat.com> (raw)
In-Reply-To: <20240305210829.943737-1-bodonnel@redhat.com>
On 3/5/24 3:08 PM, Bill O'Donnell wrote:
> Convert the minix filesystem to use the new mount API.
>
> Tested using mount and remount on minix device.
>
> Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
> ---
> fs/minix/inode.c | 64 ++++++++++++++++++++++++++++++++++--------------
> 1 file changed, 46 insertions(+), 18 deletions(-)
>
> diff --git a/fs/minix/inode.c b/fs/minix/inode.c
> index 73f37f298087..248e78a118e7 100644
> --- a/fs/minix/inode.c
> +++ b/fs/minix/inode.c
> @@ -20,11 +20,11 @@
> #include <linux/mpage.h>
> #include <linux/vfs.h>
> #include <linux/writeback.h>
> +#include <linux/fs_context.h>
>
> static int minix_write_inode(struct inode *inode,
> struct writeback_control *wbc);
> static int minix_statfs(struct dentry *dentry, struct kstatfs *buf);
> -static int minix_remount (struct super_block * sb, int * flags, char * data);
>
> static void minix_evict_inode(struct inode *inode)
> {
> @@ -111,19 +111,19 @@ static const struct super_operations minix_sops = {
> .evict_inode = minix_evict_inode,
> .put_super = minix_put_super,
> .statfs = minix_statfs,
> - .remount_fs = minix_remount,
> };
>
> -static int minix_remount (struct super_block * sb, int * flags, char * data)
> +static int minix_reconfigure(struct fs_context *fc)
> {
> - struct minix_sb_info * sbi = minix_sb(sb);
> struct minix_super_block * ms;
> + struct super_block *sb = fc->root->d_sb;
> + struct minix_sb_info * sbi = sb->s_fs_info;
>
> sync_filesystem(sb);
> ms = sbi->s_ms;
> - if ((bool)(*flags & SB_RDONLY) == sb_rdonly(sb))
> + if ((bool)(fc->sb_flags & SB_RDONLY) == sb_rdonly(sb))
> return 0;
> - if (*flags & SB_RDONLY) {
> + if (fc->sb_flags & SB_RDONLY) {
> if (ms->s_state & MINIX_VALID_FS ||
> !(sbi->s_mount_state & MINIX_VALID_FS))
> return 0;
> @@ -170,7 +170,7 @@ static bool minix_check_superblock(struct super_block *sb)
> return true;
> }
>
> -static int minix_fill_super(struct super_block *s, void *data, int silent)
> +static int minix_fill_super(struct super_block *s, struct fs_context *fc)
> {
> struct buffer_head *bh;
> struct buffer_head **map;
> @@ -180,6 +180,7 @@ static int minix_fill_super(struct super_block *s, void *data, int silent)
> struct inode *root_inode;
> struct minix_sb_info *sbi;
> int ret = -EINVAL;
> + int silent = fc->sb_flags & SB_SILENT;
>
> sbi = kzalloc(sizeof(struct minix_sb_info), GFP_KERNEL);
> if (!sbi)
> @@ -371,6 +372,39 @@ static int minix_fill_super(struct super_block *s, void *data, int silent)
> return ret;
> }
>
> +static int minix_get_tree(struct fs_context *fc)
> +{
> + return get_tree_bdev(fc, minix_fill_super);
> +}
> +
> +static void minix_free_fc(struct fs_context *fc)
> +{
> + kfree(fc->fs_private);
> +}
> +
> +struct minix_context {
> + unsigned long s_mount_opts;
This is never used. The context is typically used for storing mount
options during parsing, but minix has none, so this isn't needed.
> +};
> +
> +static const struct fs_context_operations minix_context_ops = {
> + .get_tree = minix_get_tree,
> + .reconfigure = minix_reconfigure,
> + .free = minix_free_fc,
> +};
> +
> +static int minix_init_fs_context(struct fs_context *fc)
> +{
> + struct minix_context *ctx;
> +
> + ctx = kzalloc(sizeof(struct minix_context), GFP_KERNEL);
> + if (!ctx)
> + return -ENOMEM;
> + fc->ops = &minix_context_ops;
> + fc->fs_private = ctx;
and so it doesn't need to be allocated & stored, or freed.
-Eric
next prev parent reply other threads:[~2024-03-05 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-05 21:08 [PATCH] minix: convert minix to use the new mount api Bill O'Donnell
2024-03-05 21:27 ` Eric Sandeen [this message]
2024-03-07 16:37 ` Bill O'Donnell
2024-03-05 21:29 ` Al Viro
2024-03-07 16:40 ` Bill O'Donnell
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=c4a2e820-70e5-453c-b022-a3207fb9119d@redhat.com \
--to=sandeen@redhat.com \
--cc=bodonnel@redhat.com \
--cc=brauner@kernel.org \
--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).