mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Muli Ben-Yehuda <muli@il.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: dev@sw.ru, dev@openvz.org, stable@kernel.org
Subject: Re: + sys_getppid-oopses-on-debug-kernel.patch added to -mm tree
Date: Tue, 8 Aug 2006 17:39:37 +0300	[thread overview]
Message-ID: <20060808143937.GA3953@rhun.haifa.ibm.com> (raw)
In-Reply-To: <200608081432.k78EWprf007511@shell0.pdx.osdl.net>

On Tue, Aug 08, 2006 at 07:32:51AM -0700, akpm@osdl.org wrote:
> 
> The patch titled
> 
>      sys_getppid() oopses on debug kernel
> 
> has been added to the -mm tree.  Its filename is
> 
>      sys_getppid-oopses-on-debug-kernel.patch
> 
> See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
> out what to do about this
> 
> ------------------------------------------------------
> Subject: sys_getppid() oopses on debug kernel
> From: Kirill Korotaev <dev@sw.ru>
> 
> sys_getppid() optimization can access a freed memory.  On kernels with
> DEBUG_SLAB turned ON, this results in Oops.
> 
> Signed-off-by: Kirill Korotaev <dev@openvz.org>
> Cc: <stable@kernel.org>
> Signed-off-by: Andrew Morton <akpm@osdl.org>

I'm probably missing something, but is it really valid to access freed
kernel memory even if CONFIG_DEBUG_SLAB is off - as this patch does?

Cheers,
Muli

       reply	other threads:[~2006-08-08 14:39 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 ` Muli Ben-Yehuda [this message]
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
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=20060808143937.GA3953@rhun.haifa.ibm.com \
    --to=muli@il.ibm.com \
    --cc=dev@openvz.org \
    --cc=dev@sw.ru \
    --cc=linux-kernel@vger.kernel.org \
    --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

Powered by JetHome