linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Linxuan via B4 Relay <devnull+chenlinxuan.uniontech.com@kernel.org>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Amir Goldstein <amir73il@gmail.com>,
	linux-fsdevel@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Chen Linxuan <chenlinxuan@uniontech.com>
Subject: [PATCH v3 1/3] fs: fuse: add const qualifier to fuse_ctl_file_conn_get()
Date: Fri, 09 May 2025 14:33:53 +0800	[thread overview]
Message-ID: <20250509-fusectl-backing-files-v3-1-393761f9b683@uniontech.com> (raw)
In-Reply-To: <20250509-fusectl-backing-files-v3-0-393761f9b683@uniontech.com>

From: Chen Linxuan <chenlinxuan@uniontech.com>

Add const qualifier to the file parameter in fuse_ctl_file_conn_get
function to indicate that this function does not modify the passed file
object. This improves code clarity and type safety by making the API
contract more explicit.

Signed-off-by: Chen Linxuan <chenlinxuan@uniontech.com>
---
 fs/fuse/control.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/fs/fuse/control.c b/fs/fuse/control.c
index 2a730d88cc3bdb50ea1f8a3185faad5f05fc6e74..f0874403b1f7c91571f38e4ae9f8cebe259f7dd1 100644
--- a/fs/fuse/control.c
+++ b/fs/fuse/control.c
@@ -20,7 +20,7 @@
  */
 static struct super_block *fuse_control_sb;
 
-static struct fuse_conn *fuse_ctl_file_conn_get(struct file *file)
+static struct fuse_conn *fuse_ctl_file_conn_get(const struct file *file)
 {
 	struct fuse_conn *fc;
 	mutex_lock(&fuse_mutex);

-- 
2.43.0



  reply	other threads:[~2025-05-09  6:34 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09  6:33 [PATCH v3 0/3] fuse: Expose more information of fuse backing files to userspace Chen Linxuan via B4 Relay
2025-05-09  6:33 ` Chen Linxuan via B4 Relay [this message]
2025-05-09  7:21   ` [PATCH v3 1/3] fs: fuse: add const qualifier to fuse_ctl_file_conn_get() Amir Goldstein
2025-05-09  6:33 ` [PATCH v3 2/3] fs: fuse: add backing_files control file Chen Linxuan via B4 Relay
2025-05-09  7:20   ` Amir Goldstein
2025-05-09  7:40     ` Chen Linxuan
2025-05-09  7:39   ` Chen Linxuan
2025-05-09  9:14     ` Amir Goldstein
2025-05-09 14:00   ` Miklos Szeredi
2025-05-09 14:43     ` Chen Linxuan
2025-05-09 14:59       ` Miklos Szeredi
2025-05-09 15:10         ` Chen Linxuan
2025-05-09 15:16           ` Miklos Szeredi
2025-05-11  9:55         ` Chen Linxuan
2025-05-12  8:27           ` Miklos Szeredi
2025-05-12  9:17             ` Christian Brauner
2025-05-12  9:23             ` Amir Goldstein
2025-05-12 10:06               ` Miklos Szeredi
2025-05-13  7:39                 ` Christian Brauner
2025-05-13  7:57                   ` Miklos Szeredi
2025-05-13 14:49                     ` Miklos Szeredi
2025-06-20  6:12                     ` Chen Linxuan
2025-07-02  5:11                       ` Miklos Szeredi
2025-05-09 15:19       ` Amir Goldstein
2025-05-09 15:41         ` Miklos Szeredi
2025-05-09  6:33 ` [PATCH v3 3/3] fs: fuse: add more information to fdinfo Chen Linxuan via B4 Relay
2025-05-09  6:40   ` Chen Linxuan
2025-05-09  7:13     ` Amir Goldstein
2025-05-09 16:05   ` Miklos Szeredi
2025-05-09  7:36 ` [PATCH v3 0/3] fuse: Expose more information of fuse backing files to userspace Amir Goldstein
2025-05-09 13:14   ` Miklos Szeredi
2025-05-13 18:52     ` Joanne Koong
2025-05-14  8:50       ` Miklos Szeredi
2025-05-14 23:03         ` Joanne Koong
2025-05-15  3:17           ` Chen Linxuan
2025-05-15 19:02             ` Joanne Koong

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=20250509-fusectl-backing-files-v3-1-393761f9b683@uniontech.com \
    --to=devnull+chenlinxuan.uniontech.com@kernel.org \
    --cc=amir73il@gmail.com \
    --cc=chenlinxuan@uniontech.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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).