Re: [bug] SCSI/SLUB - latest -git: WARNING: at mm/slub.c:2443 kmem_cache_destroy, scsi_put_host_cmd_pool()

Ingo Molnar
2008-04-21T13:49:44Z

* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:

> > x86.git allyesconfig bootup test produced the following warning in
> > slub.c (and a stream of similar warnings later on):
[...]

> > config and bootlog at:
> >
> > http://redhat.com/~mingo/misc/config-Sat_Apr_19_10_28_28_CEST_2008.bad
> > http://redhat.com/~mingo/misc/log-Sat_Apr_19_10_28_28_CEST_2008.bad
> >
> > [a few .config options were turned off: just accept all the defaults
> > after 'make oldconfig']
>
> The WARN_ON is caused by kmem_cache_destroy() with apparently
> outstanding objects, isn't it?
>
> The most significant piece of the log seems to be before with all
> those isa SCSI drivers ... I assume you don't actually have any of the
> hardware, you're just randomly inserting the modules?

correct. As i mentioned it in the first sentence this is an allyesconfig
bzImage bootup. I.e. this is the bootup log of a "make allyesconfig"
kernel - roughly analogous to (trying to) insert every module in
existence. In the boot log you'll find 4871 initcalls, done by over 3000
drivers that each is attempted to be loaded by the kernel (!).

I do those bootups to "run as much as possible" kernel code and to make
sure that the maximum combination of debug and other features still
produces a working kernel.

I had to work half a year to gradually get the kernel to that stage
(started with it more than a year ago, as part of the -rt kernel) but
these days i'm booting a 32-bit and a 64-bit allyesconfig bzImage kernel
almost daily :) These bootups already caught a healthy amount of bugs in
the kernel, both important and unimportant ones. Recently the size of
the allyesconfig bzImage kernel surpassed 42MB, so it's massive.

Btw., i also boot "allnoconfig" kernels. [with just the minimal set of
features turned on to make the kernel minimally boot up and report back
via networking.]

Ingo