From: Florian Weimer <fw@deneb.enyo.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Andy Lutomirski <luto@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH] Document that PF_KTHREAD _is_ ABI
Date: Sat, 20 Mar 2021 20:20:29 +0100 [thread overview]
Message-ID: <87pmztzl6q.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <YFYzPcHKWm3U04pN@localhost.localdomain> (Alexey Dobriyan's message of "Sat, 20 Mar 2021 20:39:09 +0300")
* Alexey Dobriyan:
> Some aren't -- PF_FORKNOEXEC. However it is silly for userspace to query it
> because programs knows if it forked but didn't exec without external help.
Libraries typically lack that knowledge, and may have reasons to
detect forks. But there are probably better ways than this flag, like
a MADV_WIPEONFORK mapping, or comparing counters in MAP_PRIVATE and
MAP_SHARED mappings.
next prev parent reply other threads:[~2021-03-20 19:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 16:30 [PATCH] Document that PF_KTHREAD _is_ ABI Alexey Dobriyan
2021-03-20 17:23 ` Andy Lutomirski
2021-03-20 17:39 ` Alexey Dobriyan
2021-03-20 19:20 ` Florian Weimer [this message]
2021-03-22 7:53 ` Christoph Hellwig
2021-03-31 19:23 ` Alexey Dobriyan
2021-04-01 15:05 ` Stefan Metzmacher
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=87pmztzl6q.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@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