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: Tue, 23 Sep 2008 13:28:12 +0200 From: Ingo Molnar <mingo@...e.hu> To: Srinivasa Ds <srinivasa@...ibm.com> Cc: Roland McGrath <roland@...hat.com>, linux-kernel@...r.kernel.org, akpm@...ux-foundation.org, paulus@...ba.org, linuxppc-dev@...abs.org, linux-parisc@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>, Thomas Gleixner <tglx@...utronix.de> Subject: Re: [RFC][PATCH] Demultiplexing SIGTRAP signal * Srinivasa Ds <srinivasa@...ibm.com> wrote: > On Monday 22 September 2008 20:24:04 Ingo Molnar wrote: > > * Srinivasa Ds <srinivasa@...ibm.com> wrote: > > > --- linux-2.6.27-rc7.orig/arch/ia64/include/asm/siginfo.h > > > +++ linux-2.6.27-rc7/arch/ia64/include/asm/siginfo.h > > > > please do not send patches that modify include/asm/ files, the > > include/asm-x86/ file should be modified instead. > > > > (this problem will go away in v2.6.28 when we'll move include/asm-x86/ > > to arch/x86/include/) > > > > Ingo, Sorry if I have confused you. [...] hah, indeed - i mis-read them as include/asm/. > Currently a SIGTRAP can denote any one of below reasons. > - Breakpoint hit > - H/W debug register hit > - Single step > - Signal sent through kill() or rasie() > > Architectures like powerpc/parisc provides infrastructure to > demultiplex SIGTRAP signal by passing down the information for > receiving SIGTRAP through si_code of siginfot_t structure. Here is an > attempt is generalise this infrastructure by extending it to x86 and > x86_64 archs. applied to [the new topic] tip/core/signal, thanks Srinivasa! There are some other pending x86 signal changes already, so i based tip/core/signal on tip/x86/signal. Roland, any opinion on this change? Ingo -- 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