From: Steven Rostedt <rostedt@goodmis.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
Subject: [PATCH RT] enable interrupts in do_page_fault for users.
Date: Fri, 01 Jun 2007 19:21:02 -0400 [thread overview]
Message-ID: <1180740062.21781.53.camel@localhost.localdomain> (raw)
Ingo,
To prevent scheduling while irqs disabled, I added a force to the
do_page_fault to enable interrupts.
The thing is, if the user faults at an address above PAGE_OFFSET. My
stupid program that I attached to my last email did just that:
unsigned long *p = (void*)-1;
*p = 0xbed;
where (void*)-1 is an address greater than PAGE_OFFSET. If I changed
that address to (void*)1, the program still segfaulted, but I didn't get
the warning about scheduling while interrupts disabled. I even put in a
print to show if interrupts are disabled in do_page_fault before calling
force_sig_info, and with (void*)-1 they were, and with (void*)1 they
were not disabled.
This patch forces interrupts to always be enabled when entering the user
fault code. Maybe this should also be applied to mainline?
This solves the one issue with scheduling while irqs disabled.
-- Steve
Signed-off-by: Steven Rostedt <rostedt@goodmis.org>
Index: linux-2.6.21-rt9/arch/x86_64/mm/fault.c
===================================================================
--- linux-2.6.21-rt9.orig/arch/x86_64/mm/fault.c
+++ linux-2.6.21-rt9/arch/x86_64/mm/fault.c
@@ -476,6 +476,10 @@ bad_area:
bad_area_nosemaphore:
/* User mode accesses just cause a SIGSEGV */
if (error_code & PF_USER) {
+
+ /* it's possible to have interrupts off here */
+ local_irq_enable();
+
if (is_prefetch(regs, address, error_code))
return;
next reply other threads:[~2007-06-01 23:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 23:21 Steven Rostedt [this message]
2007-06-07 1:42 ` [PATCH RT] enable interrupts in do_page_fault for users (take 2 - add i386 fix too) Steven Rostedt
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=1180740062.21781.53.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®