From: Alexey Dobriyan <adobriyan@gmail.com>
To: lennart@poettering.net
Cc: tj@kernel.org, torvalds@linux-foundation.org, carlos@redha.com,
luto@amacapital.net, akpm@linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] better visibility into kworkers
Date: Thu, 17 May 2018 10:42:02 +0300 [thread overview]
Message-ID: <20180517074202.GA3091@avx2> (raw)
> The kernel APIs for all this aren't really good
> though, and I always was reluctant to check for PF_KTHREAD, as that
> flag is neither documented for userspace, nor available in any
> userspace-accessible headers. However, I wanted to tighten this a bit,
> and hence we now define the flag in our own code, as it appeared to me
> otherwise there was no chance to ever make this fully robust.
PF_KTHREAD was introduced in 2.6.27 and its value appears to be stable
since then. I think it should be retroactively declared part of ABI
otherwise people will continue to rediscover that all other means do not
work.
Empty /proc/*/exe is second best option for systemd and it's only one
system call.
next reply other threads:[~2018-05-17 7:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 7:42 Alexey Dobriyan [this message]
2018-05-17 15:50 ` [RFC] better visibility into kworkers Lennart Poettering
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=20180517074202.GA3091@avx2 \
--to=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=carlos@redha.com \
--cc=lennart@poettering.net \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=tj@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.