[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241219023452.69907-1-laoar.shao@gmail.com>
Date: Thu, 19 Dec 2024 10:34:47 +0800
From: Yafang Shao <laoar.shao@...il.com>
To: akpm@...ux-foundation.org
Cc: torvalds@...ux-foundation.org,
pmladek@...e.com,
kvalo@...nel.org,
bp@...en8.de,
andriy.shevchenko@...ux.intel.com,
linux-mm@...ck.org,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
x86@...nel.org,
linux-snps-arc@...ts.infradead.org,
linux-wireless@...r.kernel.org,
intel-gfx@...ts.freedesktop.org,
intel-xe@...ts.freedesktop.org,
nouveau@...ts.freedesktop.org,
dri-devel@...ts.freedesktop.org,
ocfs2-devel@...ts.linux.dev,
Yafang Shao <laoar.shao@...il.com>
Subject: [PATCH v2 0/5] Remove get_task_comm() and print task comm directly
Since task->comm is guaranteed to be NUL-terminated, we can print it
directly without the need to copy it into a separate buffer. This
simplifies the code and avoids unnecessary operations.
v1->v2:
- Don't add "%pTN" (Petr, Kalle, Borislav, Andy, Linus)
v1: https://lore.kernel.org/all/20241213054610.55843-1-laoar.shao@gmail.com/
Yafang Shao (5):
kernel: Remove get_task_comm() and print task comm directly
arch: Remove get_task_comm() and print task comm directly
net: Remove get_task_comm() and print task comm directly
security: Remove get_task_comm() and print task comm directly
drivers: Remove get_task_comm() and print task comm directly
arch/arc/kernel/unaligned.c | 5 ++---
arch/x86/kernel/vm86_32.c | 5 ++---
drivers/accel/habanalabs/common/context.c | 3 +--
drivers/accel/habanalabs/common/habanalabs_ioctl.c | 11 +++--------
drivers/gpu/drm/i915/display/intel_display_driver.c | 6 ++----
drivers/gpu/drm/nouveau/nouveau_chan.c | 4 +---
drivers/gpu/drm/nouveau/nouveau_drm.c | 5 ++---
drivers/tty/tty_io.c | 3 +--
kernel/capability.c | 8 ++------
kernel/futex/waitwake.c | 3 +--
net/wireless/wext-core.c | 4 +---
security/yama/yama_lsm.c | 4 +---
12 files changed, 19 insertions(+), 42 deletions(-)
--
2.43.5
Powered by blists - more mailing lists