All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Whitcroft <apw@shadowen.org>
To: linux-kernel@vger.kernel.org
Cc: akpm@osdl.org, apw@shadowen.org
Subject: [RFC] [PATCH] add TRAP_BAD_SYSCALL_EXITS config for i386
Date: Fri, 2 Jul 2004 17:28:07 +0100	[thread overview]
Message-ID: <200407021628.i62GS7ZS002412@voidhawk.shadowen.org> (raw)

There seems to be code recently added to -bk and thereby -mm which supports
extra debug for preempt on system call exit.  Oddly there doesn't seem
to be configuration options to enable them.  Below is a possible patch
to allow enabling this on i386.  Sadly the most obvious menu to add this
to is the Kernel Hacking menu, but that is defined in architecture specific
configuration.  If this makes sense I could patch the other arches?

Comments?

-apw

=== 8< ===
Add a configuration option to allow enabling TRAP_BAD_SYSCALL_EXITS to the
Kernel Hacking menu.

Revision: $Rev: 356 $

Signed-off-by: Andy Whitcroft <apw@shadowen.org>

---
 Kconfig |    7 +++++++
 1 files changed, 7 insertions(+)

diff -upN reference/arch/i386/Kconfig current/arch/i386/Kconfig
--- reference/arch/i386/Kconfig	2004-07-02 14:00:51.000000000 +0100
+++ current/arch/i386/Kconfig	2004-07-02 16:40:49.000000000 +0100
@@ -1492,6 +1492,13 @@ config X86_MPPARSE
 	depends on X86_LOCAL_APIC && !X86_VISWS
 	default y
 
+config TRAP_BAD_SYSCALL_EXITS
+	bool "Debug bad system call exits"
+	help
+	  If you say Y here the kernel will check for system calls which
+	  return without clearing preempt.
+        default n
+
 endmenu
 
 source "security/Kconfig"

             reply	other threads:[~2004-07-02 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 16:28 Andy Whitcroft [this message]
2004-07-02 23:32 ` [RFC] [PATCH] add TRAP_BAD_SYSCALL_EXITS config for i386 Andrew Morton
2004-07-07 13:55   ` Andy Whitcroft

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200407021628.i62GS7ZS002412@voidhawk.shadowen.org \
    --to=apw@shadowen.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.