From: Ingo Molnar <mingo@elte.hu>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: linux-kernel@vger.kernel.org,
Pekka Enberg <penberg@cs.helsinki.fi>,
Christoph Lameter <clameter@sgi.com>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: [bug] SCSI/SLUB - latest -git: WARNING: at mm/slub.c:2443 kmem_cache_destroy, scsi_put_host_cmd_pool()
Date: Tue, 22 Apr 2008 15:10:20 +0200 [thread overview]
Message-ID: <20080422131020.GB7311@elte.hu> (raw)
In-Reply-To: <1208793440.3640.22.camel@localhost.localdomain>
* James Bottomley <James.Bottomley@HansenPartnership.com> wrote:
> Thanks ... it looks like we may have trouble from devices that alter
> the unchecked isa dma flag after scsi_host_alloc. The guilty parties
> appear to be gdth, eata, u14-34f, ultrastor, BusLogic and advansys.
>
> The trouble is that if you alloc the host with it one way and free it
> with it the other, the wrong freelist is used and the ref counts are
> invalid.
>
> Try this pseudo fix: it avoids allocating the freelist until add time
> (by which time they should all have fixed the flag). It still doesn't
> change the fact that the host is allocated in the wrong region, but
> that shouldn't matter too much.
ok - do you intend to push this pseudo-fix upstream? If yes then please
consider it fixed as far as i'm concerned - i'll re-reply if the warning
resurfaces (it wasnt lethal to the bootup otherwise). Or if you've got
some other approach/fix then i can test that too.
Ingo
next prev parent reply other threads:[~2008-04-22 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080419085758.GA18612@elte.hu>
2008-04-19 13:22 ` [bug] SCSI/SLUB - latest -git: WARNING: at mm/slub.c:2443 kmem_cache_destroy, scsi_put_host_cmd_pool() James Bottomley
2008-04-21 13:49 ` Ingo Molnar
2008-04-21 15:57 ` James Bottomley
2008-04-22 13:10 ` Ingo Molnar [this message]
2008-04-22 13:39 ` James Bottomley
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=20080422131020.GB7311@elte.hu \
--to=mingo@elte.hu \
--cc=James.Bottomley@HansenPartnership.com \
--cc=clameter@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
/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