From: "Ted Ts'o" <tytso@mit.edu>
To: Kees Cook <keescook@google.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: Correct way to include siginfo.h?
Date: Tue, 27 Mar 2012 10:37:44 -0700 [thread overview]
Message-ID: <20120327173744.GD10142@thunk.org> (raw)
In-Reply-To: <CAGXu5jJx85b2ysgx2aXWUUf4dJMc34Cukp3S1VKiC_Pc5U2+Pw@mail.gmail.com>
On Tue, Mar 27, 2012 at 10:29:39AM -0700, Kees Cook wrote:
>
> I'm trying to get at the future seccomp fields on siginfo_t, namely
> "si_syscall":
Ah, I didn't realize you were trying to do that. siginfo_t has been
stable since forever, and so I think we've always depending on glibc
to export the structure. As a result I don't know that much effort
has been made to make siginfo.h safe for any userspace user other than
glibc.
Silly question; we're not going to actually change the size of the
siginfo_t structure in a userspace visible way, are we? I don't know
of are any shared libraries that fill in a siginfo_t structure passed
in by the caller (which could be located on the stack), but it's
certainly possible that such library ABI's could exist.
- Ted
next prev parent reply other threads:[~2012-03-27 17:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 17:01 Correct way to include siginfo.h? Kees Cook
2012-03-27 17:21 ` Ted Ts'o
2012-03-27 17:29 ` Kees Cook
2012-03-27 17:37 ` Ted Ts'o [this message]
2012-03-27 18:01 ` Kees Cook
2012-03-29 17:58 ` H. Peter Anvin
2012-03-29 18:13 ` Kees Cook
2012-03-29 18:14 ` H. Peter Anvin
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=20120327173744.GD10142@thunk.org \
--to=tytso@mit.edu \
--cc=keescook@google.com \
--cc=linux-kernel@vger.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