[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A956FB3.5030400@zytor.com>
Date: Wed, 26 Aug 2009 10:24:03 -0700
From: "H. Peter Anvin" <hpa@...or.com>
To: Peter Zijlstra <peterz@...radead.org>
CC: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Frederic Weisbecker <fweisbec@...il.com>,
Hendrik Brueckner <brueckner@...ux.vnet.ibm.com>,
Jason Baron <jbaron@...hat.com>, linux-kernel@...r.kernel.org,
mingo@...e.hu, laijs@...fujitsu.com, rostedt@...dmis.org,
jiayingz@...gle.com, mbligh@...gle.com, lizf@...fujitsu.com,
Heiko Carstens <heiko.carstens@...ibm.com>,
Martin Schwidefsky <schwidefsky@...ibm.com>,
Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [PATCH 08/12] add trace events for each syscall entry/exit
On 08/26/2009 12:10 AM, Peter Zijlstra wrote:
> On Tue, 2009-08-25 at 14:31 -0400, Mathieu Desnoyers wrote:
>> For instance, some
>> proprietary Linux driver does very odd things with system calls within
>> kernel threads, like invoking them with int 0x80.
>
> So who is going to send the x86 patch to make int 0x80 from kernel space
> panic the machine? :-)
Panicing might be a pretty darn good idea, since $DEITY knows what state
your stacks are in at that point, and if it is about to overflow.
... besides all the other evilness that entails.
-hpa
--
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
--
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/
Powered by blists - more mailing lists