lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 18 Nov 2009 13:18:29 -0800 (PST) From: Roland McGrath <roland@...hat.com> To: Masami Hiramatsu <mhiramat@...hat.com> Cc: Ingo Molnar <mingo@...e.hu>, lkml <linux-kernel@...r.kernel.org>, Oleg Nesterov <oleg@...hat.com>, systemtap <systemtap@...rces.redhat.com>, DLE <dle-develop@...ts.sourceforge.net> Subject: Re: [PATCH -tip 0/3] tracepoint: Add signal events > Roland McGrath wrote: > > I would add the siginfo_t * argument to each of these tracepoints. > > I see. Is it OK to record only si_errno and si_code? because si_signo > might be as same as sig. Yes, si_signo will match sig. Which siginfo_t fields are interesting to record can vary by signal (i.e. by si_code). si_code and si_errno are certainly the first things that come to mind as most useful. For SI_TIMER, si_tid, si_overrun, and si_sigval are interesting. For others, si_pid and si_uid are interesting. Thanks, Roland -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists