From: Yafang Shao <laoar.shao@gmail.com>
To: akpm@linux-foundation.org
Cc: torvalds@linux-foundation.org, pmladek@suse.com,
kvalo@kernel.org, bp@alien8.de,
andriy.shevchenko@linux.intel.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, x86@kernel.org,
linux-snps-arc@lists.infradead.org,
linux-wireless@vger.kernel.org, intel-gfx@lists.freedesktop.org,
intel-xe@lists.freedesktop.org, nouveau@lists.freedesktop.org,
dri-devel@lists.freedesktop.org, ocfs2-devel@lists.linux.dev,
Yafang Shao <laoar.shao@gmail.com>
Subject: [PATCH v2 0/5] Remove get_task_comm() and print task comm directly
Date: Thu, 19 Dec 2024 10:34:47 +0800 [thread overview]
Message-ID: <20241219023452.69907-1-laoar.shao@gmail.com> (raw)
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
next reply other threads:[~2024-12-19 2:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 2:34 Yafang Shao [this message]
2024-12-19 2:34 ` [PATCH v2 1/5] kernel: " Yafang Shao
2024-12-19 2:34 ` [PATCH v2 2/5] arch: " Yafang Shao
2024-12-19 2:34 ` [PATCH v2 3/5] net: " Yafang Shao
2024-12-19 2:34 ` [PATCH v2 4/5] security: " Yafang Shao
2024-12-19 2:34 ` [PATCH v2 5/5] drivers: " 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=20241219023452.69907-1-laoar.shao@gmail.com \
--to=laoar.shao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=nouveau@lists.freedesktop.org \
--cc=ocfs2-devel@lists.linux.dev \
--cc=pmladek@suse.com \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.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