From: Erik Mouw <erik@harddisk-recovery.com>
To: Andrew Vasquez <andrew.vasquez@qlogic.com>
Cc: Or Gerlitz <or.gerlitz@gmail.com>,
linux-scsi@vger.kernel.org, rmk@arm.linux.org.uk, axboe@suse.de,
linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: Re: [BUG 2.6.17-git] kmem_cache_create: duplicate cache scsi_cmd_cache
Date: Fri, 12 May 2006 22:18:36 +0200 [thread overview]
Message-ID: <20060512201835.GB29077@harddisk-recovery.com> (raw)
In-Reply-To: <20060512172729.GA2321@andrew-vasquezs-powerbook-g4-15.local>
On Fri, May 12, 2006 at 10:27:29AM -0700, Andrew Vasquez wrote:
> On Fri, 12 May 2006, Erik Mouw wrote:
> > I tracked it down with git bisect. The culprit is this commit:
> >
> > 56cf6504fc1c0c221b82cebc16a444b684140fb7 is first bad commit
> > diff-tree 56cf6504fc1c0c221b82cebc16a444b684140fb7 (from
> > d98550e334715b2d9e45f8f0f4e1608720108640)
> > Author: Russell King <rmk@dyn-67.arm.linux.org.uk>
> > Date: Fri May 5 17:57:52 2006 +0100
> >
> > [BLOCK] Fix oops on removal of SD/MMC card
> >
> > The block layer keeps a reference (driverfs_dev) to the struct
> > device associated with the block device, and uses it internally
> > for generating uevents in block_uevent.
> >
> > Block device uevents include umounting the partition, which can
> > occur after the backing device has been removed.
> ...
>
> THat's really weird... I reported a completely unrelated problem some
> days ago:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=114728598328769&w=2
AFAICS it's the same bug. Apparently you can trigger it with any scsi
host driver.
Erik
--
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands
next prev parent reply other threads:[~2006-05-12 20:18 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-11 15:14 [BUG 2.6.17-git] kmem_cache_create: duplicate cache scsi_cmd_cache Erik Mouw
2006-05-12 4:53 ` Or Gerlitz
2006-05-12 17:16 ` Erik Mouw
2006-05-12 17:27 ` Andrew Vasquez
2006-05-12 20:18 ` Erik Mouw [this message]
2006-05-12 17:36 ` Linus Torvalds
2006-05-12 17:47 ` James Bottomley
2006-05-12 18:58 ` James Bottomley
2006-05-12 19:09 ` Linus Torvalds
2006-05-12 20:38 ` Russell King
2006-05-12 20:50 ` Linus Torvalds
2006-05-12 20:58 ` Russell King
2006-05-12 21:27 ` Linus Torvalds
2006-05-12 21:46 ` Linus Torvalds
2006-05-12 21:51 ` Russell King
2006-05-12 22:15 ` Linus Torvalds
2006-05-12 22:37 ` Linus Torvalds
2006-05-12 23:57 ` Greg KH
2006-05-14 16:01 ` Russell King
2006-05-12 21:18 ` Greg KH
2006-05-12 21:32 ` Linus Torvalds
2006-05-12 22:45 ` Greg KH
2006-05-12 20:52 ` Greg KH
2006-05-12 21:03 ` Russell King
2006-05-12 21:34 ` Greg KH
2006-05-12 21:39 ` Al Viro
2006-05-12 20:30 ` Erik Mouw
2006-05-12 20:37 ` Russell King
2006-05-12 20:21 ` Erik Mouw
2006-05-12 20:34 ` Russell King
2006-05-12 21:43 ` Al Viro
2006-05-12 21:55 ` Russell King
2006-05-12 22:08 ` Al Viro
2006-05-12 22:22 ` Linus Torvalds
2006-05-12 22:28 ` Al Viro
2006-05-12 22:48 ` Al Viro
2006-05-12 22:51 ` Al Viro
2006-05-12 23:04 ` Linus Torvalds
2006-05-12 23:21 ` Al Viro
2006-05-12 23:37 ` Al Viro
2006-05-12 23:50 ` Linus Torvalds
2006-05-13 0:20 ` Al Viro
2006-05-24 14:07 ` Erik Mouw
2006-05-13 0:08 ` Greg KH
2006-05-12 22:37 ` Russell King
2006-05-12 21:58 ` Al Viro
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=20060512201835.GB29077@harddisk-recovery.com \
--to=erik@harddisk-recovery.com \
--cc=andrew.vasquez@qlogic.com \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=or.gerlitz@gmail.com \
--cc=rmk@arm.linux.org.uk \
--cc=torvalds@osdl.org \
/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