linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Long Li <leo.lilong@huawei.com>
To: Bernd Schubert <bernd@bsbernd.com>, <leo.lilong@huaweicloud.com>,
	<miklos@szeredi.hu>
Cc: <linux-fsdevel@vger.kernel.org>, <yi.zhang@huawei.com>,
	<yangerkun@huawei.com>, <lonuxli.64@gmail.com>
Subject: Re: [PATCH] fuse: show io_uring mount option in /proc/mounts
Date: Sat, 12 Jul 2025 09:02:42 +0800	[thread overview]
Message-ID: <aHG0MhIc_UE6xGE2@localhost.localdomain> (raw)
In-Reply-To: <b33a4493-1b77-42b5-aac9-b0af0833a131@bsbernd.com>

On Wed, Jul 09, 2025 at 01:00:05PM +0200, Bernd Schubert wrote:
> 
> 
> On 7/9/25 04:02, leo.lilong@huaweicloud.com wrote:
> > From: Long Li <leo.lilong@huawei.com>
> > 
> > When mounting a FUSE filesystem with io_uring option and using io_uring
> > for communication, this option was not shown in /proc/mounts or mount
> > command output. This made it difficult for users to verify whether
> > io_uring was being used for communication in their FUSE mounts.
> > 
> > Add io_uring to the list of mount options displayed in fuse_show_options()
> > when the fuse-over-io_uring feature is enabled and being used.
> > 
> > Signed-off-by: Long Li <leo.lilong@huawei.com>
> > ---
> >  fs/fuse/inode.c | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c
> > index ecb869e895ab..a6a8cd84fdde 100644
> > --- a/fs/fuse/inode.c
> > +++ b/fs/fuse/inode.c
> > @@ -913,6 +913,8 @@ static int fuse_show_options(struct seq_file *m, struct dentry *root)
> >  			seq_puts(m, ",default_permissions");
> >  		if (fc->allow_other)
> >  			seq_puts(m, ",allow_other");
> > +		if (fc->io_uring)
> > +			seq_puts(m, ",io_uring");
> >  		if (fc->max_read != ~0)
> >  			seq_printf(m, ",max_read=%u", fc->max_read);
> >  		if (sb->s_bdev && sb->s_blocksize != FUSE_DEFAULT_BLKSIZE)
> 
> I agree with you that is impossible to see, but issue is that io_uring
> is not a mount option. Maybe we should add a sysfs file?
> 

Yes, this is not a mount option. Thank you for your suggestion.

Thanks,
Long Li

      parent reply	other threads:[~2025-07-12  1:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-09  2:02 [PATCH] fuse: show io_uring mount option in /proc/mounts leo.lilong
2025-07-09 11:00 ` Bernd Schubert
2025-07-09 17:55   ` Joanne Koong
2025-07-10 11:27     ` Christian Brauner
2025-07-12  1:02   ` Long Li [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=aHG0MhIc_UE6xGE2@localhost.localdomain \
    --to=leo.lilong@huawei.com \
    --cc=bernd@bsbernd.com \
    --cc=leo.lilong@huaweicloud.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=lonuxli.64@gmail.com \
    --cc=miklos@szeredi.hu \
    --cc=yangerkun@huawei.com \
    --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;
as well as URLs for NNTP newsgroup(s).