On Mon, Jun 14, 2010 at 07:10:06AM +0200, Michael Kerrisk wrote: > >> * It's incomplete. If you compare against the corresponding > >> information in sigaction(2) [better pull the latest page from git for > >> this comparison], there is more information about which fields are set > >> by the various signals. Also, various siginfo_t fields (si_signo) are > >> missing from your table. > > > > Ok it could be listed. > > This was an example. I didn't check for all incomplete pieces. What else should be missing? I generated the table by looking at the trap handlers. > >> Likewise, it suggests that there is useful info in si_trapno, but > >> usually there is not. The entry for SIGKILL also seems strange. > > > > There is useful information in trapno for the signals where > > I listed it. > > So, there may be a problem here. sigaction.2 currently states > > int si_trapno; /* Trap number that caused > hardware-generated signal > (unused on most architectures) */ > > Is the last line true? Checking this, my reading of the source is that It's not true. I think it's also needed in some cases to figure out what exactly happened, although in most cases code gives this information. > si_trapno is only used on SPARC/MIPS/Alpha. (These are the > architectures that define __ARCH_SI_TRAPNO) Is that wrong? In > particular, x86 doesn't generally seem to set si_trapno, right? arch/x86/kernel/signal.c:162: put_user_ex(current->thread.trap_no, &sc->trapno); > > > Why is SIGKILL strange? > > I suspect that this should be a more general statement about signals > sent with kill(2), right? There's nothing special about SIGKILL in > this respect, AFAIK. By the way, the sigaction.2 page, has a statement > that covers this. It was more a comparison to non KILL signals, but ok you're right RT signals would need to be listed too. -Andi -- ak@xxxxxxxxxxxxxxx -- Speaking for myself only. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
