Messages in this thread | | | Date | Tue, 27 Mar 2012 10:29:39 -0700 | Subject | Re: Correct way to include siginfo.h? | From | Kees Cook <> |
| |
On Tue, Mar 27, 2012 at 10:21 AM, Ted Ts'o <tytso@mit.edu> 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 "si_syscall":
static void reporter(int nr, siginfo_t *info, void *void_context) { ... syscall = info->si_syscall;
> http://git.kernel.org/?p=fs/ext2/e2fsprogs.git;a=blob;f=e2fsck/sigcatcher.c;h=10b93287d5b2b4da1fb43d34fafd848d06c01645;hb=5f7c04972fefa8198c34f231a9e8a5430705b4ab > > The sigcatcher.c file is a debugging tool for e2fsprogs that prints > pretty much everything that is available to userspace, as far as I > know...
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.
-Kees
-- Kees Cook Chrome OS Security -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |