From: Suchit Karunakaran <suchitkarunakaran@gmail.com>
To: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
linux-fsdevel@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, skhan@linuxfoundation.org,
linux-kernel-mentees@lists.linux.dev,
Suchit Karunakaran <suchitkarunakaran@gmail.com>
Subject: [PATCH] fs/namespace: describe @pinned parameter in do_lock_mount()
Date: Thu, 21 Aug 2025 22:49:05 +0530 [thread overview]
Message-ID: <20250821171905.10251-1-suchitkarunakaran@gmail.com> (raw)
Add a description for the @pinned parameter in do_lock_mount() to suppress
a compiler warning. No functional changes
Signed-off-by: Suchit Karunakaran <suchitkarunakaran@gmail.com>
---
fs/namespace.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/fs/namespace.c b/fs/namespace.c
index 0a5fec7065d7..52394a2ebaf3 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -2738,6 +2738,9 @@ static int attach_recursive_mnt(struct mount *source_mnt,
/**
* do_lock_mount - lock mount and mountpoint
* @path: target path
+ * @pinned: holds a reference to the mountpoint pinned during the
+ * mount operation to prevent it from being unmounted or
+ * moved concurrently
* @beneath: whether the intention is to mount beneath @path
*
* Follow the mount stack on @path until the top mount @mnt is found. If
--
2.50.1
reply other threads:[~2025-08-21 17:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250821171905.10251-1-suchitkarunakaran@gmail.com \
--to=suchitkarunakaran@gmail.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).