All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>, akpm@osdl.org
Subject: Re: [Oops] 2.6.10: PREEMPT SMP
Date: Fri, 04 Feb 2005 11:43:00 +0000	[thread overview]
Message-ID: <11365.1107517380@redhat.com> (raw)
In-Reply-To: <1107188868.6675.29.camel@gonzales>


Xavier Bestel <xavier.bestel@free.fr> wrote:

> I just got this Oops with 2.6.10 (debian/sid stock kernel).
> 
> Kernel is tainted by VMWare, but it wasn't used (machine powered on
> remotely and used just to run gaim though ssh). I can perhaps try to
> reproduce it without it though if you need.

Hmmm... I see it involves the key stuff I wrote.

I don't think it can be a problem with preemption interfering with the key
management code accessing the key tree; every access to the tree outside of
the bootup initialisation is made with the appropriate spinlock held - and
that disables preemption.

It seems unlikely to be a double free... keys aren't freed the moment their
usage count reaches zero; a separate daemon is enlisted to go through the tree
when there's something to dispose of and extract and free all unused keys.

However, it's not impossible that there's a race there that I can't see
(though it doesn't look likely). Are you willing to try patching your kernel
with something? If so, if you can look through security/keys/key.c, and every
time you see a line saying:

	kmem_cache_free(key_jar, key);

insert this line before it:

	memset(key, 0xbb, sizeof(*key);

This will corrupt the memory that held the dead key before freeing it. Then if
something is touching a dead key, the pattern 0xbbbbbbbb or similar will crop
up in a register or on the stack, and the kernel will very likely crash.

David

  reply	other threads:[~2005-02-04 11:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-31 16:27 [Oops] 2.6.10: PREEMPT SMP Xavier Bestel
2005-02-04 11:43 ` David Howells [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-02-18 11:29 Klaus Steinberger
2005-03-08 20:50 Andrew Taylor
2005-03-21 23:35 ` Andrew Morton
2005-03-24  0:42   ` Andrew Taylor

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=11365.1107517380@redhat.com \
    --to=dhowells@redhat.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xavier.bestel@free.fr \
    /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.