linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill O'Donnell <bodonnel@redhat.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-fsdevel@vger.kernel.org, al@alarsen.net,
	brauner@kernel.org, sandeen@redhat.com
Subject: Re: [PATCH] qnx4: convert qnx4 to use the new mount api
Date: Tue, 27 Feb 2024 18:20:05 -0600	[thread overview]
Message-ID: <Zd58NdyYetuVakMi@redhat.com> (raw)
In-Reply-To: <ff9e0d7b-49e7-4c4d-95d1-76bbf8b0b685@sandeen.net>

On Tue, Feb 27, 2024 at 04:49:04PM -0600, Eric Sandeen wrote:
> On 2/26/24 4:46 PM, Bill O'Donnell wrote:
> > Convert the qnx4 filesystem to use the new mount API.
> > 
> > Tested mount, umount, and remount using a qnx4 boot image.
> > 
> > Signed-off-by: Bill O'Donnell <bodonnel@redhat.com>
> > ---
> >  fs/qnx4/inode.c | 49 +++++++++++++++++++++++++++++++------------------
> >  1 file changed, 31 insertions(+), 18 deletions(-)
> > 
> > diff --git a/fs/qnx4/inode.c b/fs/qnx4/inode.c
> > index 6eb9bb369b57..c36fbe45a0e9 100644
> > --- a/fs/qnx4/inode.c
> > +++ b/fs/qnx4/inode.c
> > @@ -21,6 +21,7 @@
> >  #include <linux/buffer_head.h>
> >  #include <linux/writeback.h>
> >  #include <linux/statfs.h>
> > +#include <linux/fs_context.h>
> >  #include "qnx4.h"
> >  
> >  #define QNX4_VERSION  4
> > @@ -30,28 +31,33 @@ static const struct super_operations qnx4_sops;
> >  
> >  static struct inode *qnx4_alloc_inode(struct super_block *sb);
> >  static void qnx4_free_inode(struct inode *inode);
> > -static int qnx4_remount(struct super_block *sb, int *flags, char *data);
> >  static int qnx4_statfs(struct dentry *, struct kstatfs *);
> > +static int qnx4_get_tree(struct fs_context *fc);
> >  
> >  static const struct super_operations qnx4_sops =
> >  {
> >  	.alloc_inode	= qnx4_alloc_inode,
> >  	.free_inode	= qnx4_free_inode,
> >  	.statfs		= qnx4_statfs,
> > -	.remount_fs	= qnx4_remount,
> >  };
> >  
> > -static int qnx4_remount(struct super_block *sb, int *flags, char *data)
> > +static int qnx4_reconfigure(struct fs_context *fc)
> >  {
> > -	struct qnx4_sb_info *qs;
> > +	struct super_block *sb = fc->root->d_sb;
> > +	struct qnx4_sb_info *qs = sb->s_fs_info;
> 
> You assign *qs here at declaration
>   
> >  	sync_filesystem(sb);
> >  	qs = qnx4_sb(sb);
> 
> and then reassign it here (qnx4_sb() just gets sb->s_fs_info as well)
> 
> Don't need both, I'd stick with just the uninitialized *qs as was
> originally in qnx4_remount().

I did wonder about that. I'll submit a v2. Thanks for your review.
-Bill

> 
> The rest looks fine to me,
> -Eric
> 
> 


      reply	other threads:[~2024-02-28  0:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-26 22:46 [PATCH] qnx4: convert qnx4 to use the new mount api Bill O'Donnell
2024-02-27 12:23 ` Christian Brauner
2024-02-27 12:26 ` Christian Brauner
2024-02-27 23:54   ` Eric Sandeen
2024-02-27 12:43 ` Anders Larsen
2024-02-27 22:49 ` Eric Sandeen
2024-02-28  0:20   ` Bill O'Donnell [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=Zd58NdyYetuVakMi@redhat.com \
    --to=bodonnel@redhat.com \
    --cc=al@alarsen.net \
    --cc=brauner@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=sandeen@sandeen.net \
    /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).