From: Peter Zijlstra <peterz@infradead.org>
To: Yafang Shao <laoar.shao@gmail.com>
Cc: pmladek@suse.com, keescook@chromium.org, viro@zeniv.linux.org.uk,
akpm@linux-foundation.org, valentin.schneider@arm.com,
mathieu.desnoyers@efficios.com, qiang.zhang@windriver.com,
robdclark@chromium.org, christian@brauner.io,
dietmar.eggemann@arm.com, mingo@redhat.com,
juri.lelli@redhat.com, vincent.guittot@linaro.org,
rostedt@goodmis.org, bsegall@google.com, mgorman@suse.de,
bristot@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/4] sched.h: extend task comm from 16 to 24 for CONFIG_BASE_FULL
Date: Thu, 7 Oct 2021 14:54:07 +0200 [thread overview]
Message-ID: <YV7t748s8vJQS9Bi@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20211007120752.5195-4-laoar.shao@gmail.com>
On Thu, Oct 07, 2021 at 12:07:51PM +0000, Yafang Shao wrote:
> Besides the in-tree kthreads listed above, the out-of-tree kthreads may
> also be truncated:
>
> rtase_work_queu
> nvidia-modeset/
> UVM global queu
> UVM deferred re
> ...
>
Fundamentally we don't give a crap about out of tree stuff. And their
behaviour or not should be of absolutely no concern what so ever for any
patch ever.
next prev parent reply other threads:[~2021-10-07 12:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-07 12:07 [PATCH v2 0/4] task_struct: extend task comm from 16 to 24 for CONFIG_BASE_FULL Yafang Shao
2021-10-07 12:07 ` [PATCH v2 1/4] cn_proc.h: use TASK_COMM_LEN instread of 16 in struct proc_event Yafang Shao
2021-10-07 14:51 ` Kees Cook
2021-10-07 15:09 ` Kees Cook
2021-10-07 15:45 ` Yafang Shao
2021-10-07 12:07 ` [PATCH v2 2/4] fs/exec: use strscpy instead of strlcpy in __set_task_comm Yafang Shao
2021-10-07 14:52 ` Kees Cook
2021-10-07 12:07 ` [PATCH v2 3/4] sched.h: extend task comm from 16 to 24 for CONFIG_BASE_FULL Yafang Shao
2021-10-07 12:54 ` Peter Zijlstra [this message]
2021-10-07 13:02 ` Yafang Shao
2021-10-07 14:56 ` Kees Cook
2021-10-07 15:47 ` Yafang Shao
2021-10-07 12:07 ` [PATCH v2 4/4] kernel/kthread: show a warning if kthread's comm is truncated Yafang Shao
2021-10-07 15:01 ` Kees Cook
2021-10-07 17:41 ` Steven Rostedt
2021-10-08 12: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=YV7t748s8vJQS9Bi@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=christian@brauner.io \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=keescook@chromium.org \
--cc=laoar.shao@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pmladek@suse.com \
--cc=qiang.zhang@windriver.com \
--cc=robdclark@chromium.org \
--cc=rostedt@goodmis.org \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=viro@zeniv.linux.org.uk \
/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