public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kirill Korotaev <dev@sw.ru>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: "Muli Ben-Yehuda" <muli@il.ibm.com>,
	"Björn Steinbrink" <B.Steinbrink@gmx.de>,
	linux-kernel@vger.kernel.org, dev@openvz.org, stable@kernel.org
Subject: Re: + sys_getppid-oopses-on-debug-kernel.patch added to -mm tree
Date: Tue, 08 Aug 2006 19:39:52 +0400	[thread overview]
Message-ID: <44D8B048.8060103@sw.ru> (raw)
In-Reply-To: <1155050547.5729.91.camel@localhost.localdomain>

>>Even without getting into just how ugly this is, is it really worth
>>it?
it is impossible to run debug kernels w/o this patch :/
or are you asking whether this optimization worth it?

What makes me worry is that this is a sign that vendors
don't even bother to run debug kernels :((((

> It never was in my opinion but I lost that battle to Linus in 1.3.40 or
> so timescales. Given how critical getppid _isnt_ I don't see the point
> in being clever.
Alan, if you sign off the patch I will prepare another one, which removes
the optimization away and make it always safe.

Kirill


  reply	other threads:[~2006-08-08 15:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200608081432.k78EWprf007511@shell0.pdx.osdl.net>
2006-08-08 14:39 ` + sys_getppid-oopses-on-debug-kernel.patch added to -mm tree Muli Ben-Yehuda
2006-08-08 14:51   ` Björn Steinbrink
2006-08-08 14:57     ` Muli Ben-Yehuda
2006-08-08 15:22       ` Alan Cox
2006-08-08 15:39         ` Kirill Korotaev [this message]
2006-08-08 16:36           ` Dave Jones
2006-08-09  8:12             ` Kirill Korotaev
2006-08-09 17:38               ` Dave Jones
2006-08-10  9:35                 ` Kirill Korotaev

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=44D8B048.8060103@sw.ru \
    --to=dev@sw.ru \
    --cc=B.Steinbrink@gmx.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dev@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.com \
    --cc=stable@kernel.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