linux-kernel - [PATCH] Update NSIGTRAP in asm-generic/siginfo.h

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>] [day] [month] [year] [list]

Date:	Sat, 4 Apr 2009 19:38:49 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	linux-kernel@...r.kernel.org, srinivasa@...ibm.com
Cc:	akpm@...l.org
Subject: [PATCH] Update NSIGTRAP in asm-generic/siginfo.h

Update NSIGTRAP in asm-generic/siginfo.h

Impact: (nearly) trivial

The patch

commit da654b74bda14c45a7d98c731bf3c1a43b6b74e2
Author: Srinivasa Ds <srinivasa@...ibm.com>
Date:   Tue Sep 23 15:23:52 2008 +0530

    signals: demultiplexing SIGTRAP signal

forgot to update the NSIGTRAP define in asm-generic/siginfo.h to 
the new number of sigtrap subcodes. Nothing in the tree seems to use it, 
but presumably something in user space might. So update it.

Cc: Srinivasa Ds <srinivasa@...ibm.com>

Signed-off-by: Andi Kleen <ak@...ux.intel.com>

---
 include/asm-generic/siginfo.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: linux-2.6.29-ak/include/asm-generic/siginfo.h
===================================================================
--- linux-2.6.29-ak.orig/include/asm-generic/siginfo.h	2008-10-24 13:34:57.000000000 +0200
+++ linux-2.6.29-ak/include/asm-generic/siginfo.h	2009-04-04 19:35:23.000000000 +0200
@@ -201,7 +201,7 @@
 #define TRAP_TRACE	(__SI_FAULT|2)	/* process trace trap */
 #define TRAP_BRANCH     (__SI_FAULT|3)  /* process taken branch trap */
 #define TRAP_HWBKPT     (__SI_FAULT|4)  /* hardware breakpoint/watchpoint */
-#define NSIGTRAP	2
+#define NSIGTRAP	4
 
 /*
  * SIGCHLD si_codes
--
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/