[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231031114728.41485-1-bagasdotme@gmail.com>
Date: Tue, 31 Oct 2023 18:47:28 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Filesystems Development <linux-fsdevel@...r.kernel.org>
Cc: Alexander Viro <viro@...iv.linux.org.uk>,
Christian Brauner <brauner@...nel.org>,
Jan Kara <jack@...e.cz>, Yusong Gao <a869920004@....com>,
Bagas Sanjaya <bagasdotme@...il.com>
Subject: [PATCH] fs: Clarify "non-RCY" in access_override_creds() comment
The term is originally intended as a joke that stands for "non-racy".
This trips new contributors who mistake it for RCU typo [1].
Replace the term with more-explicit wording.
Link: https://lore.kernel.org/r/20231030-debatten-nachrangig-f58abcdac530@brauner/
Signed-off-by: Bagas Sanjaya <bagasdotme@...il.com>
---
fs/open.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/fs/open.c b/fs/open.c
index 98f6601fbac65e..a89c64629aacf4 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -442,7 +442,8 @@ static const struct cred *access_override_creds(void)
* 'get_current_cred()' function), that will clear the
* non_rcu field, because now that other user may be
* expecting RCU freeing. But normal thread-synchronous
- * cred accesses will keep things non-RCY.
+ * cred accesses will keep things non-racy to avoid RCU
+ * freeing.
*/
override_cred->non_rcu = 1;
base-commit: 7f680e5f256f346a5d3cd83a17c84bb6bc950008
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists