From: Jani Nikula <jani.nikula@linux.intel.com>
To: Yafang Shao <laoar.shao@gmail.com>, akpm@linux-foundation.org
Cc: torvalds@linux-foundation.org, ebiederm@xmission.com,
alexei.starovoitov@gmail.com, rostedt@goodmis.org,
catalin.marinas@arm.com, penguin-kernel@i-love.sakura.ne.jp,
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: Re: [PATCH resend v4 00/11] Improve the copy of task comm
Date: Mon, 29 Jul 2024 12:29:43 +0300 [thread overview]
Message-ID: <87bk2gzgu0.fsf@intel.com> (raw)
In-Reply-To: <20240729023719.1933-1-laoar.shao@gmail.com>
On Mon, 29 Jul 2024, Yafang Shao <laoar.shao@gmail.com> wrote:
> Hello Andrew,
>
> Is it appropriate for you to apply this to the mm tree?
>
> 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.
Why are we normalizing calling double-underscore prefixed functions all
over the place? i.e. __get_task_comm().
get_task_comm() is widely used. At a glance, looks like it could be used
in many of the patches here too.
BR,
Jani.
>
> 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~#6: kstrdup
> PATCH #7~#9: strncpy
> PATCH #10~#11: strcpy
>
> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> Link: https://lore.kernel.org/all/CAHk-=wjAmmHUg6vho1KjzQi2=psR30+CogFd4aXrThr2gsiS4g@mail.gmail.com/ [0]
>
> Changes:
> v3->v4:
> - Rename __kstrndup() to __kmemdup_nul() and define it inside mm/util.c
> (Matthew)
> - Remove unused local varaible (Simon)
>
> v2->v3: https://lore.kernel.org/all/20240621022959.9124-1-laoar.shao@gmail.com/
> - Deduplicate code around kstrdup (Andrew)
> - Add commit log for dropping task_lock (Catalin)
>
> v1->v2: https://lore.kernel.org/bpf/20240613023044.45873-1-laoar.shao@gmail.com/
> - 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 (11):
> 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/util: Deduplicate code in {kstrdup,kstrndup,kmemdup_nul}
> 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 | 61 ++++++++++++---------------
> net/ipv6/ndisc.c | 2 +-
> security/lsm_audit.c | 4 +-
> security/selinux/selinuxfs.c | 2 +-
> tools/bpf/bpftool/pids.c | 2 +
> 14 files changed, 51 insertions(+), 58 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-07-29 9:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-29 2:37 [PATCH resend v4 00/11] Improve the copy of task comm Yafang Shao
2024-07-29 2:37 ` [PATCH v4 01/11] fs/exec: Drop task_lock() inside __get_task_comm() Yafang Shao
2024-07-29 2:37 ` [PATCH v4 02/11] auditsc: Replace memcpy() with __get_task_comm() Yafang Shao
2024-07-29 2:37 ` [PATCH v4 03/11] security: " Yafang Shao
2024-07-29 2:37 ` [PATCH v4 04/11] bpftool: Ensure task comm is always NUL-terminated Yafang Shao
2024-07-29 2:37 ` [PATCH v4 05/11] mm/util: Fix possible race condition in kstrdup() Yafang Shao
2024-07-29 2:37 ` [PATCH v4 06/11] mm/util: Deduplicate code in {kstrdup,kstrndup,kmemdup_nul} Yafang Shao
2024-07-29 2:37 ` [PATCH v4 07/11] mm/kmemleak: Replace strncpy() with __get_task_comm() Yafang Shao
2024-07-29 2:37 ` [PATCH v4 08/11] tsacct: " Yafang Shao
2024-07-29 2:37 ` [PATCH v4 09/11] tracing: " Yafang Shao
2024-07-29 2:37 ` [PATCH v4 10/11] net: Replace strcpy() " Yafang Shao
2024-07-29 2:37 ` [PATCH v4 11/11] drm: " Yafang Shao
2024-07-29 9:29 ` Jani Nikula [this message]
2024-07-29 11:45 ` [PATCH resend v4 00/11] Improve the copy of task comm Yafang Shao
2024-07-31 0:59 ` Andrew Morton
2024-07-31 2:14 ` 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=87bk2gzgu0.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=alexei.starovoitov@gmail.com \
--cc=audit@vger.kernel.org \
--cc=bpf@vger.kernel.org \
--cc=catalin.marinas@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=ebiederm@xmission.com \
--cc=laoar.shao@gmail.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=penguin-kernel@i-love.sakura.ne.jp \
--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).