mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Pekka Enberg" <penberg@cs.helsinki.fi>
To: "Dave Jones" <davej@redhat.com>,
	"Linux Kernel" <linux-kernel@vger.kernel.org>,
	"Luca Risolia" <luca.risolia@studio.unibo.it>
Subject: Re: sn9c10x list corruption in 2.6.18.1
Date: Sun, 22 Oct 2006 23:37:06 +0300	[thread overview]
Message-ID: <84144f020610221337k2137a1a9xeb35a4bce48e152c@mail.gmail.com> (raw)
In-Reply-To: <20061022031145.GA24855@redhat.com>

On 10/22/06, Dave Jones <davej@redhat.com> wrote:
> What's odd here is that we have a list entry still on a list, with its ->next set to
> LIST_POISON2, which should only ever happen after an entry has been removed from
> a list.  The list manipulation in cache_alloc_refill is all done under l3->list_lock,
> so I'm puzzled how this is possible.
>
> I found one area in the driver where we do list manipulation without any locking,
> but I'm not entirely convinced that this is the source of the bug yet.

But I don't see how that could cause a slab list to go bad. An
old-fashioned slab corruption sounds more like it. Does the the kernel
have CONFIG_SLAB_DEBUG enabled?

                                    Pekka

  parent reply	other threads:[~2006-10-22 20:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-22  3:11 Dave Jones
2006-10-22 11:46 ` Luca Risolia
2006-10-22 18:15   ` Dave Jones
2006-10-22 21:22     ` Luca Risolia
2006-10-23  2:35       ` teunis
2006-10-23 11:37         ` Luca Risolia
2006-10-23  2:39       ` teunis
2006-10-22 20:37 ` Pekka Enberg [this message]
2006-10-22 20:54   ` Dave Jones

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=84144f020610221337k2137a1a9xeb35a4bce48e152c@mail.gmail.com \
    --to=penberg@cs.helsinki.fi \
    --cc=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luca.risolia@studio.unibo.it \
    /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®