Linux filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Bernd Schubert <bernd@bsbernd.com>
Cc: miklos@szeredi.hu, joannelkoong@gmail.com,
	fuse-devel@lists.linux.dev, neal@gompa.dev,
	linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 1/1] mount_service: use the mount_flags table instead of declaring our own
Date: Fri, 8 May 2026 10:59:45 -0700	[thread overview]
Message-ID: <20260508175945.GE2241589@frogsfrogsfrogs> (raw)
In-Reply-To: <45b102f5-423f-40de-887a-a54772a8504b@bsbernd.com>

On Fri, May 08, 2026 at 06:51:45PM +0200, Bernd Schubert wrote:
> 
> 
> On 5/8/26 00:14, Darrick J. Wong wrote:
> > From: Darrick J. Wong <djwong@kernel.org>
> > 
> > Use the canonical mount flags table in mount_util.c instead of
> > opencoding our own version in mount_service.c.
> > 
> > Signed-off-by: "Darrick J. Wong" <djwong@kernel.org>
> > ---
> >  util/mount_service.c |   51 +++++++++++++-------------------------------------
> >  1 file changed, 13 insertions(+), 38 deletions(-)
> > 
> > 
> > diff --git a/util/mount_service.c b/util/mount_service.c
> > index 8c9747b3928a51..79e5b060ba3356 100644
> > --- a/util/mount_service.c
> > +++ b/util/mount_service.c
> > @@ -1457,73 +1457,48 @@ struct ms_to_mount_map {
> >  	unsigned int mount_attr_flag;
> >  };
> >  
> > -static const struct ms_to_mount_map attrs[] = {
> > -	{ MS_RDONLY,		MOUNT_ATTR_RDONLY },
> > -	{ MS_NOSUID,		MOUNT_ATTR_NOSUID },
> > -	{ MS_NODEV,		MOUNT_ATTR_NODEV },
> > -	{ MS_NOEXEC,		MOUNT_ATTR_NOEXEC },
> > -	{ MS_RELATIME,		MOUNT_ATTR_RELATIME },
> > -	{ MS_NOATIME,		MOUNT_ATTR_NOATIME },
> > -	{ MS_STRICTATIME,	MOUNT_ATTR_STRICTATIME },
> > -	{ MS_NODIRATIME,	MOUNT_ATTR_NODIRATIME },
> > -#ifdef MOUNT_ATTR_NOSYMFOLLOW
> > -	{ MS_NOSYMFOLLOW,	MOUNT_ATTR_NOSYMFOLLOW },
> > -#endif
> > -	{ 0, 0 },
> > -};
> > -
> >  static void get_mount_attr_flags(const struct fuse_service_mount_command *oc,
> >  				 unsigned int *attr_flags,
> >  				 unsigned long *leftover_ms_flags)
> >  {
> > -	const struct ms_to_mount_map *i;
> > +	const struct mount_flags *i;
> >  	unsigned int ms_flags = ntohl(oc->ms_flags);
> >  	unsigned int mount_attr_flags = 0;
> >  
> > -	for (i = attrs; i->ms_flag != 0; i++) {
> > -		if (ms_flags & i->ms_flag)
> > -			mount_attr_flags |= i->mount_attr_flag;
> > -		ms_flags &= ~i->ms_flag;
> > +	for (i = mount_flags; i->opt != NULL; i++) {
> > +		if (!i->on || !(ms_flags & i->flag))
> > +			continue;
> > +
> > +		mount_attr_flags |= i->mount_attr;
> > +		ms_flags &= ~i->flag;
> >  	}
> >  
> >  	*leftover_ms_flags = ms_flags;
> >  	*attr_flags = mount_attr_flags;
> >  }
> >  
> > -struct ms_to_str_map {
> > -	unsigned long ms_flag;
> > -	const char *string;
> > -};
> > -
> > -static const struct ms_to_str_map strflags[] = {
> > -	{ MS_SYNCHRONOUS,	"sync" },
> > -	{ MS_DIRSYNC,		"dirsync" },
> > -	{ MS_LAZYTIME,		"lazytime" },
> > -	{ 0, 0 },
> > -};
> > -
> >  static int set_ms_flags(struct mount_service *mo, unsigned long ms_flags)
> >  {
> > -	const struct ms_to_str_map *i;
> > +	const struct mount_flags *i;
> >  	int ret;
> >  
> > -	for (i = strflags; i->ms_flag != 0; i++) {
> > -		if (!(ms_flags & i->ms_flag))
> > +	for (i = mount_flags; i->opt != NULL; i++) {
> > +		if (!i->on || !(ms_flags & i->flag))
> >  			continue;
> >  
> > -		ret = fsconfig(mo->fsopenfd, FSCONFIG_SET_FLAG, i->string,
> > +		ret = fsconfig(mo->fsopenfd, FSCONFIG_SET_FLAG, i->opt,
> >  			       NULL, 0);
> >  		if (ret) {
> >  			int error = errno;
> >  
> >  			fprintf(stderr, "%s: set %s option: %s\n",
> > -				mo->msgtag, i->string, strerror(error));
> > +				mo->msgtag, i->opt, strerror(error));
> >  			emit_fsconfig_messages(mo);
> >  
> >  			errno = error;
> >  			return -1;
> >  		}
> > -		ms_flags &= ~i->ms_flag;
> > +		ms_flags &= ~i->flag;
> >  	}
> >  
> >  	/*
> > 
> > 
> 
> 
> Hi Darrick,
> 
> wouldn't it make sense to use the functions from mount_fsmount.c? I can
> also clean this up later if you want.

Oh, hah!  Yes, I'll revise this patch to use them.

> I guess this doesn't handle the case for "ro" going into fsmount() and
> fsconfig() yet - update now or later?

That'll become another fix patch for mount_service.c.

--D

> 
> Thanks,
> Bernd
> 
> 
> 
> 

  reply	other threads:[~2026-05-08 17:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-07 22:13 [PATCHSET 2/2] libfuse: new mount service container fixes Darrick J. Wong
2026-05-07 22:14 ` [PATCH 1/1] mount_service: use the mount_flags table instead of declaring our own Darrick J. Wong
2026-05-08 16:51   ` Bernd Schubert
2026-05-08 17:59     ` Darrick J. Wong [this message]
2026-05-09  0:48       ` Darrick J. Wong
2026-05-09  7:42         ` Bernd Schubert
2026-05-08 17:05 ` [PATCHSET 2/2] libfuse: new mount service container fixes Bernd Schubert
2026-05-08 17:12   ` Bernd Schubert
2026-05-08 17:50     ` Bernd Schubert
2026-05-09  0:43   ` Darrick J. Wong

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=20260508175945.GE2241589@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=bernd@bsbernd.com \
    --cc=fuse-devel@lists.linux.dev \
    --cc=joannelkoong@gmail.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=neal@gompa.dev \
    /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