Re: Correct way to include siginfo.h?
From: Kees Cook
Date: Tue Mar 27 2012 - 13:29:36 EST
On Tue, Mar 27, 2012 at 10:21 AM, Ted Ts'o <tytso@xxxxxxx> wrote:
> On Tue, Mar 27, 2012 at 10:01:10AM -0700, Kees Cook wrote:
>> Does anyone know the right way to include siginfo.h when building
>> userspace tools that need it?
> What fields or structures are you trying to get at? I haven't needed
> to include siginfo.h explicitly even though this file pokes and prods
> pretty thoroughly at the siginfo structures:
I'm trying to get at the future seccomp fields on siginfo_t, namely
static void reporter(int nr, siginfo_t *info, void *void_context)
syscall = info->si_syscall;
> The sigcatcher.c file is a debugging tool for e2fsprogs that prints
> pretty much everything that is available to userspace, as far as I
Yeah, it looks like you're leaning on glibc's signal.h (and its
bits/signal.h file), which has its own siginfo definition rather than
attempting to include one from the kernel.
Chrome OS Security
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/