From: "Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>
To: Andi Kleen <ak@suse.de>
Cc: prasanna@in.ibm.com, akpm@osdl.org, linux-kernel@vger.kernel.org,
jbeulich@novell.com
Subject: Re: [PATCH 1/2] i386: Disallow kprobes on NMI handlers - try #2
Date: Thu, 10 Aug 2006 21:00:10 +0900 [thread overview]
Message-ID: <1155211210.4141.16.camel@localhost.localdomain> (raw)
In-Reply-To: <200608101352.08828.ak@suse.de>
On Thu, 2006-08-10 at 13:52 +0200, Andi Kleen wrote:
> On Thursday 10 August 2006 13:36, Fernando Luis Vázquez Cao wrote:
> > A kprobe executes IRET early and that could cause NMI recursion and stack
> > corruption.
> >
> > Note: This problem was originally spotted and solved by Andi Kleen in the
> > x86_64 architecture. This patch is an adaption of his patch for i386.
>
> Originally Jan Beulich discovered these classes of bugs actually
Sorry for the mistake Jan.
> I applied the two patches (after fixing lots of rejects because that
> code had already changed a lot). But I have my doubts it is complete.
>
> e.g. the NMI watchdog nmi code has lots of callees which you don't
> handle (notifier chains, spinlocks, printks which can call practically everything, ...)
>
> The printk in the NMI handler look pretty bogus so I just removed it.
I had done the same in my local repository (^-^).
> But all the other code would be tricky. but .e.g. marking up
> spinlocks would be probably not a good idea.
>
> When we oops (call die) perhaps we can force kprobes to be disabled?
>
> Also everybody hooking into the die chain would need to be covered too.
>
> Probably some followon work is needed.
Agreed. In fact I am currently working on that. I sent the previous
patches just to get started.
Thank you,
Fernando
prev parent reply other threads:[~2006-08-10 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-10 11:36 Fernando Luis Vázquez Cao
2006-08-10 11:52 ` Andi Kleen
2006-08-10 12:00 ` Fernando Luis Vázquez Cao [this message]
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=1155211210.4141.16.camel@localhost.localdomain \
--to=fernando@oss.ntt.co.jp \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=prasanna@in.ibm.com \
/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®