From: "Robert Święcki" <robert@swiecki.net>
To: Kees Cook <keescook@chromium.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
Jann Horn <jannh@google.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>,
linux-api@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-hardening@vger.kernel.org
Subject: Re: [RFC] Get siginfo from unreaped task
Date: Sat, 12 Feb 2022 12:23:55 +0100 [thread overview]
Message-ID: <CAP145phC6S6Zda-ZWLH1s4ZfDPh79rtf_7vzs-yvt1vykUCP4A@mail.gmail.com> (raw)
In-Reply-To: <20220212042843.2993537-1-keescook@chromium.org>
sob., 12 lut 2022 o 05:28 Kees Cook <keescook@chromium.org> napisał(a):
>
> Make siginfo available through PTRACE_GETSIGINFO after process death,
> without needing to have already used PTRACE_ATTACH. Uses 48 more bytes
> in task_struct, though I bet there might be somewhere else we could
> stash a copy of it?
An alternative way of accessing this info could be abusing the
waitid() interface, with some additional, custom to Linux, flag
waitid(P_ALL, 0, &si, __WCHILDSIGINFO);
which would change what is put into si.
But maybe ptrace() is better, because it's mostly incompatible with
other OSes anyway on the behavior/flag level, while waitd() seems to
be POSIX/BSD standard, even if Linux specifies some additional flags.
--
Robert Święcki
next prev parent reply other threads:[~2022-02-12 11:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-12 4:28 [RFC] Get siginfo from unreaped task Kees Cook
2022-02-12 11:23 ` Robert Święcki [this message]
2022-02-13 2:32 ` Andy Lutomirski
2022-02-13 8:52 ` Christian Brauner
2022-02-14 20:07 ` Kees Cook
2022-02-14 22:08 ` Robert Święcki
2022-02-15 9:01 ` Christian Brauner
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=CAP145phC6S6Zda-ZWLH1s4ZfDPh79rtf_7vzs-yvt1vykUCP4A@mail.gmail.com \
--to=robert@swiecki.net \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=wad@chromium.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;
as well as URLs for NNTP newsgroup(s).