From: Yafang Shao <laoar.shao@gmail.com>
To: torvalds@linux-foundation.org
Cc: ebiederm@xmission.com, alexei.starovoitov@gmail.com,
rostedt@goodmis.org, linux-mm@kvack.org,
linux-fsdevel@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, audit@vger.kernel.org,
linux-security-module@vger.kernel.org, selinux@vger.kernel.org,
bpf@vger.kernel.org, netdev@vger.kernel.org,
dri-devel@lists.freedesktop.org,
Yafang Shao <laoar.shao@gmail.com>,
Quentin Monnet <qmo@kernel.org>
Subject: [PATCH v2 04/10] bpftool: Ensure task comm is always NUL-terminated
Date: Thu, 13 Jun 2024 10:30:38 +0800 [thread overview]
Message-ID: <20240613023044.45873-5-laoar.shao@gmail.com> (raw)
In-Reply-To: <20240613023044.45873-1-laoar.shao@gmail.com>
Let's explicitly ensure the destination string is NUL-terminated. This way,
it won't be affected by changes to the source string.
Signed-off-by: Yafang Shao <laoar.shao@gmail.com>
Reviewed-by: Quentin Monnet <qmo@kernel.org>
---
tools/bpf/bpftool/pids.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tools/bpf/bpftool/pids.c b/tools/bpf/bpftool/pids.c
index 9b898571b49e..23f488cf1740 100644
--- a/tools/bpf/bpftool/pids.c
+++ b/tools/bpf/bpftool/pids.c
@@ -54,6 +54,7 @@ static void add_ref(struct hashmap *map, struct pid_iter_entry *e)
ref = &refs->refs[refs->ref_cnt];
ref->pid = e->pid;
memcpy(ref->comm, e->comm, sizeof(ref->comm));
+ ref->comm[sizeof(ref->comm) - 1] = '\0';
refs->ref_cnt++;
return;
@@ -77,6 +78,7 @@ static void add_ref(struct hashmap *map, struct pid_iter_entry *e)
ref = &refs->refs[0];
ref->pid = e->pid;
memcpy(ref->comm, e->comm, sizeof(ref->comm));
+ ref->comm[sizeof(ref->comm) - 1] = '\0';
refs->ref_cnt = 1;
refs->has_bpf_cookie = e->has_bpf_cookie;
refs->bpf_cookie = e->bpf_cookie;
--
2.39.1
next prev parent reply other threads:[~2024-06-13 2:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 2:30 [PATCH v2 00/10] Improve the copy of task comm Yafang Shao
2024-06-13 2:30 ` [PATCH v2 01/10] fs/exec: Drop task_lock() inside __get_task_comm() Yafang Shao
2024-06-13 2:30 ` [PATCH v2 02/10] auditsc: Replace memcpy() with __get_task_comm() Yafang Shao
2024-06-13 2:30 ` [PATCH v2 03/10] security: " Yafang Shao
2024-06-13 2:30 ` Yafang Shao [this message]
2024-06-13 2:30 ` [PATCH v2 05/10] mm/util: Fix possible race condition in kstrdup() Yafang Shao
2024-06-13 21:14 ` Andrew Morton
2024-06-13 22:17 ` Linus Torvalds
2024-06-14 2:41 ` Yafang Shao
2024-06-14 2:33 ` Yafang Shao
2024-06-13 2:30 ` [PATCH v2 06/10] mm/kmemleak: Replace strncpy() with __get_task_comm() Yafang Shao
2024-06-13 8:37 ` Catalin Marinas
2024-06-13 12:10 ` Yafang Shao
2024-06-14 10:57 ` Catalin Marinas
2024-06-14 11:45 ` Yafang Shao
2024-06-13 2:30 ` [PATCH v2 07/10] tsacct: " Yafang Shao
2024-06-13 2:30 ` [PATCH v2 08/10] tracing: " Yafang Shao
2024-06-13 2:30 ` [PATCH v2 09/10] net: Replace strcpy() " Yafang Shao
2024-06-13 2:30 ` [PATCH v2 10/10] drm: " Yafang Shao
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=20240613023044.45873-5-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=audit@vger.kernel.org \
--cc=bpf@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiederm@xmission.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=qmo@kernel.org \
--cc=rostedt@goodmis.org \
--cc=selinux@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/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).