linux-kernel - [PATCH 0/5] kernel: Standardize task comm setup for kthreads

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-Id: <20230213010020.1813-1-michael.christie@oracle.com>
Date:   Sun, 12 Feb 2023 19:00:15 -0600
From:   Mike Christie <michael.christie@...cle.com>
To:     brauner@...nel.org, ebiederm@...ssion.com,
        torvalds@...ux-foundation.org, linux-kernel@...r.kernel.org
Subject: [PATCH 0/5] kernel: Standardize task comm setup for kthreads

The following patches were made over Linus's tree. They standardize the
task->comm initialization. Currently, kthreads will set it up after a
successful kthread_thread call in the calling function. io_uring will
set it from the thread fn. And the vhost task patches added it's own
helper.

This patchset adds a new kernel clone args callout, setup_thread_fn,
which can be used to setup an internal struct, like is needed by
kthreads, and can also be used to set the task->comm like is needed
by kthread, io_uring and vhost.

Note that I have not yet compile tested all the archs in the first
patch. I was not sure if Linus was going to prefer this patchset's
approach to setting the comm or would like to leave it as it is now.
So this more of a RFC.