mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Davi Arnaut <davi.lkml@gmail.com>
To: Andrew Morton <akpm@osdl.org>
Cc: greearb@candelatech.com, linux-kernel@vger.kernel.org,
	Manfred Spraul <manfred@colorfullife.com>
Subject: Re: kernel BUG at mm/slab.c:1488! (2.6.13.2)
Date: Fri, 28 Oct 2005 08:36:20 -0200	[thread overview]
Message-ID: <750c918d0510280336g67344787r66a9aba4753e22cb@mail.gmail.com> (raw)
In-Reply-To: <20051027215312.57303595.akpm@osdl.org>

On 10/28/05, Andrew Morton <akpm@osdl.org> wrote:
> Davi Arnaut <davi.lkml@gmail.com> wrote:
> >
> >  > It seems that something still tries to load the ext3 module, and I get the
> >  > BUG seen below.  If I remove the ext3 module and re-build the initrd,
> >  > the error goes away.
>
> Yes, I think the kernel is overreacting here.
>
> Manfred, what sayest thou?
>
> (nb: untested)
>
>
> From: Andrew Morton <akpm@osdl.org>
>
> slab presently goes BUG if someone tries to register an already-registered
> cache.
>
> But this can happen if the user accidentally loads a module which is already
> statically linked into the kernel.  Nuking the kernel is rather a harsh
> reaction.
>
> Change it into a warning, and just fail the kmem_cache_alloc() attempt.  If
> the module is well-behaved, the modprobe will fail and all is well.

How about really fixing kmem_cache_* to use the proper return conventions ?
In this case it should have returned ERR_PTR(-EEXIST);

> Notes:
>
> - Swaps the ranking of cache_chain_sem and lock_cpu_hotplug().  Doesn't seem
>   important.
>
>
> <sniped>
>

  reply	other threads:[~2005-10-28 10:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-28  3:32 Davi Arnaut
2005-10-28  4:53 ` Andrew Morton
2005-10-28 10:36   ` Davi Arnaut [this message]
2005-10-28 10:55     ` Andrew Morton
2005-10-29 11:37   ` Manfred Spraul
  -- strict thread matches above, loose matches on Subject: below --
2005-10-27 20:55 Ben Greear
2005-10-27 21:37 ` Nate Diller

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=750c918d0510280336g67344787r66a9aba4753e22cb@mail.gmail.com \
    --to=davi.lkml@gmail.com \
    --cc=akpm@osdl.org \
    --cc=greearb@candelatech.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manfred@colorfullife.com \
    /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®