linux-kernel - Re: [RFC][PATCH] Demultiplexing SIGTRAP signal -v2

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 23 Sep 2008 17:53:58 +0200
From:	Gabriel Paubert <paubert@...m.es>
To:	Srinivasa Ds <srinivasa@...ibm.com>
Cc:	Ingo Molnar <mingo@...e.hu>, linux-parisc@...r.kernel.org,
	linux-kernel@...r.kernel.org, linuxppc-dev@...abs.org,
	paulus@...ba.org, "H. Peter Anvin" <hpa@...or.com>,
	akpm@...ux-foundation.org, Thomas Gleixner <tglx@...utronix.de>,
	Roland McGrath <roland@...hat.com>
Subject: Re: [RFC][PATCH] Demultiplexing SIGTRAP signal -v2

On Tue, Sep 23, 2008 at 07:55:01PM +0530, Srinivasa Ds wrote:
> On Tuesday 23 September 2008 17:00:01 Ingo Molnar wrote:
> 
> > > 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.
> >
> > -tip testing found the following build error with the attached config:
> >
> 
> Ingo, Reproduced build break issue with your config on tip tree. It was a costly overlook 
> to miss one header file. I included it in this patch and tested it out.
> 
> 
> 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()

Typo: s/rasie/raise/

No strong opinion about the patch, but more info is usually better.

	Regards,
	Gabriel
--
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/