From: James Bottomley <James.Bottomley@SteelEye.com>
To: Dave Jones <davej@redhat.com>
Cc: linux-scsi@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: Re: USB/SCSI slab corruption.
Date: Thu, 12 Jan 2006 19:30:32 -0600 [thread overview]
Message-ID: <1137115833.3530.46.camel@mulgrave> (raw)
In-Reply-To: <20060112233606.GP19827@redhat.com>
On Thu, 2006-01-12 at 18:36 -0500, Dave Jones wrote:
> > SCSI device sdb: 321672960 512-byte hdwr sectors (164697 MB)
> > slab error in cache_free_debugcheck(): cache `sgpool-8': double free, or
> > memory outside object was overwritten
> > [<c0153593>] cache_free_debugcheck+0x1ab/0x22f [<c014d3c2>]
> > mempool_free+0x3a/0x73
> > [<c01540e2>] kmem_cache_free+0x2a/0x69 [<c014d3c2>]
> > mempool_free+0x3a/0x73
> > [<f8862c8b>] scsi_io_completion+0x207/0x4d2 [scsi_mod] [<f885dcad>]
This is a classic symptom of done() being called twice on the same
command. Best guess would be a driver issue.
James
prev parent reply other threads:[~2006-01-13 1:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 23:36 USB/SCSI slab corruption Dave Jones
2006-01-13 0:23 ` Stefan Richter
2006-01-13 9:39 ` F. Poncin
2006-01-13 1:30 ` James Bottomley [this message]
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=1137115833.3530.46.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=davej@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/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