From: Cabbaken Q <Cabbaken@outlook.com>
To: Kees Cook <kees@kernel.org>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Christian Brauner <brauner@kernel.org>, Jan Kara <jack@suse.cz>
Subject: [PATCH] Fix comment style of `do_execveat_common()`
Date: Mon, 14 Apr 2025 07:07:57 +0000 [thread overview]
Message-ID: <OS7PR01MB116815D7D0BCF55F3FE216293DFB32@OS7PR01MB11681.jpnprd01.prod.outlook.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
From 46fab5ecc860f26f790bec2a902a54bae58dfca7 Mon Sep 17 00:00:00 2001
From: Ruoyu Qiu <cabbaken@outlook.com>
Date: Mon, 14 Apr 2025 14:56:28 +0800
Subject: [PATCH] Fix comment style of `do_execveat_common()`
Signed-off-by: Ruoyu Qiu <cabbaken@outlook.com>
---
fs/exec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/exec.c b/fs/exec.c
index 8e4ea5f1e64c..51dad7af5083 100644
--- a/fs/exec.c
+++ b/fs/exec.c
@@ -1903,7 +1903,7 @@ static int do_execveat_common(int fd, struct filename *filename,
/*
* We move the actual failure in case of RLIMIT_NPROC excess from
* set*uid() to execve() because too many poorly written programs
- * don't check setuid() return code. Here we additionally recheck
+ * don't check setuid() return code. Here we additionally recheck
* whether NPROC limit is still exceeded.
*/
if ((current->flags & PF_NPROC_EXCEEDED) &&
--
2.49.0
[-- Attachment #2: Type: text/html, Size: 5917 bytes --]
next reply other threads:[~2025-04-14 7:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-14 7:07 Cabbaken Q [this message]
2025-04-14 13:58 ` Jan Kara
2025-04-14 17:07 ` Matthew Wilcox
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=OS7PR01MB116815D7D0BCF55F3FE216293DFB32@OS7PR01MB11681.jpnprd01.prod.outlook.com \
--to=cabbaken@outlook.com \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=kees@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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