mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Avi Kivity <avi@qumranet.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [git pull] core, x86: make LIST_POISON less deadly
Date: Mon, 14 Jul 2008 19:08:48 +0300	[thread overview]
Message-ID: <487B7A10.9050104@qumranet.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807140856130.3305@woody.linux-foundation.org>

Linus Torvalds wrote:
>> We dont do any instruction decoding in #GP handlers to figure out what 
>> happened, while in the pagefault case we know which address faulted, 
>> etc.
>>     
>
> Why would we care? It would be very obvious from the instruction 
> disassembly plus the register contents. No need to decode instructions.
>   

We could add a printk to the #GP handler that alerts the reader that a 
poisoned list is suspected, if we find the address pattern in one of the 
registers.

-- 
error compiling committee.c: too many arguments to function


  parent reply	other threads:[~2008-07-14 16:08 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 14:48 Ingo Molnar
2008-07-14 15:03 ` Linus Torvalds
2008-07-14 15:12   ` Ingo Molnar
2008-07-14 15:53     ` Avi Kivity
2008-07-14 15:59     ` Linus Torvalds
2008-07-14 16:07       ` Ingo Molnar
2008-07-14 16:08       ` Avi Kivity [this message]
2008-07-14 16:26         ` Linus Torvalds
2008-07-14 16:34           ` Ingo Molnar
2008-07-14 18:33       ` Andi Kleen
2008-07-14 18:42         ` Linus Torvalds
2008-07-14 19:11           ` Andi Kleen
2008-07-14 19:30             ` Linus Torvalds
2008-07-14 19:42               ` Andi Kleen
2008-07-14 18:35   ` Andi Kleen
2008-07-14 18:42     ` Linus Torvalds

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=487B7A10.9050104@qumranet.com \
    --to=avi@qumranet.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@linux-foundation.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 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®