All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: pageexec@freemail.hu
Cc: Willy Tarreau <w@1wt.eu>,
	marcelo@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86_64: another fix for canonical RIPs during signal handling
Date: Fri, 23 Jun 2006 14:29:04 +0200	[thread overview]
Message-ID: <200606231429.04909.ak@suse.de> (raw)
In-Reply-To: <449BC808.4174.277D15CF@pageexec.freemail.hu>


> 
> that's not true. if the application expects to crash due to a bad
> signal handler then rip=0 may or may not achieve that, depending on
> what mapping exists at that address - this is inconsistent behaviour
> (from userland's point of view) created by the kernel itself, hence
> this is a kernel bug and should be fixed.

If it "wants" to crash it can just jump to 0 (or whatever unmapped address
it has) by itself. No need to involve the kernel here.

The only point of the patch was to not make the kernel/CPU crash due 
to CPU bugs triggered by applications. But we really
don't care what happens to the application when it corrupts its stack frame.

-Andi

  parent reply	other threads:[~2006-06-23 12:33 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-22 21:06 [PATCH] x86_64: another fix for canonical RIPs during signal handling Willy Tarreau
2006-06-22 21:26 ` Andi Kleen
2006-06-22 21:33   ` Willy Tarreau
2006-06-22 22:17     ` Andi Kleen
     [not found]     ` <449BC808.4174.277D15CF@pageexec.freemail.hu>
2006-06-23 12:29       ` Andi Kleen [this message]
     [not found]       ` <449C0616.4382.286F7C8C@pageexec.freemail.hu>
2006-06-23 13:32         ` Willy Tarreau
2006-06-23 13:46           ` Andi Kleen
2006-06-23 13:52             ` Willy Tarreau
2006-06-23 14:51           ` Alan Cox

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=200606231429.04909.ak@suse.de \
    --to=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@kvack.org \
    --cc=pageexec@freemail.hu \
    --cc=w@1wt.eu \
    /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.