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>
Subject: [PATCH v2 00/10] Improve the copy of task comm
Date: Thu, 13 Jun 2024 10:30:34 +0800 [thread overview]
Message-ID: <20240613023044.45873-1-laoar.shao@gmail.com> (raw)
Using {memcpy,strncpy,strcpy,kstrdup} to copy the task comm relies on the
length of task comm. Changes in the task comm could result in a destination
string that is overflow. Therefore, we should explicitly ensure the destination
string is always NUL-terminated, regardless of the task comm. This approach
will facilitate future extensions to the task comm.
As suggested by Linus [0], we can identify all relevant code with the
following git grep command:
git grep 'memcpy.*->comm\>'
git grep 'kstrdup.*->comm\>'
git grep 'strncpy.*->comm\>'
git grep 'strcpy.*->comm\>'
PATCH #2~#4: memcpy
PATCH #5: kstrdup
PATCH #6~#8: strncpy
PATCH #9~#10: strcpy
Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
Link: https://lore.kernel.org/all/CAHk-=wjAmmHUg6vho1KjzQi2=psR30+CogFd4aXrThr2gsiS4g@mail.gmail.com/ [0]
Changes:
v1->v2:
- Add comment for dropping task_lock() in __get_task_comm() (Alexei)
- Drop changes in trace event (Steven)
- Fix comment on task comm (Matus)
v1: https://lore.kernel.org/all/20240602023754.25443-1-laoar.shao@gmail.com/
Yafang Shao (10):
fs/exec: Drop task_lock() inside __get_task_comm()
auditsc: Replace memcpy() with __get_task_comm()
security: Replace memcpy() with __get_task_comm()
bpftool: Ensure task comm is always NUL-terminated
mm/util: Fix possible race condition in kstrdup()
mm/kmemleak: Replace strncpy() with __get_task_comm()
tsacct: Replace strncpy() with __get_task_comm()
tracing: Replace strncpy() with __get_task_comm()
net: Replace strcpy() with __get_task_comm()
drm: Replace strcpy() with __get_task_comm()
drivers/gpu/drm/drm_framebuffer.c | 2 +-
drivers/gpu/drm/i915/i915_gpu_error.c | 2 +-
fs/exec.c | 10 ++++++++--
include/linux/sched.h | 4 ++--
kernel/auditsc.c | 6 +++---
kernel/trace/trace.c | 2 +-
kernel/trace/trace_events_hist.c | 2 +-
kernel/tsacct.c | 2 +-
mm/kmemleak.c | 8 +-------
mm/util.c | 4 +++-
net/ipv6/ndisc.c | 2 +-
security/lsm_audit.c | 4 ++--
security/selinux/selinuxfs.c | 2 +-
tools/bpf/bpftool/pids.c | 2 ++
14 files changed, 28 insertions(+), 24 deletions(-)
--
2.39.1
next 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 Yafang Shao [this message]
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 ` [PATCH v2 04/10] bpftool: Ensure task comm is always NUL-terminated Yafang Shao
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-1-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=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).