public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@SteelEye.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
	Or Gerlitz <or.gerlitz@gmail.com>,
	linux-scsi@vger.kernel.org, rmk@arm.linux.org.uk, axboe@suse.de,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [BUG 2.6.17-git] kmem_cache_create: duplicate cache scsi_cmd_cache
Date: Fri, 12 May 2006 13:58:45 -0500	[thread overview]
Message-ID: <1147460325.3769.46.camel@mulgrave.il.steeleye.com> (raw)
In-Reply-To: <1147456038.3769.39.camel@mulgrave.il.steeleye.com>

On Fri, 2006-05-12 at 12:47 -0500, James Bottomley wrote:
> I'll look at the release paths and see if I can work out what it is.

OK, here's the scoop.  The problem patch adds a get of driverfs_dev in
add_disk(), but doesn't put it again until disk_release() (which occurs
on final put_disk() of the gendisk).

However, in SCSI, the driverfs_dev is the sdev_gendev.  That means
there's a reference held on sdev_gendev  until final disk put.
Unfortunately, we use the driver model driver_remove to trigger
del_gendisk (which removes the gendisk from visibility and decrements
the refcount), so we've introduced an unbreakable deadlock in the
reference counting with this.

I suggest simply reversing this patch at the moment.  If Russell and
Jens can tell me what they're trying to do I'll see if there's another
way to do it.

James



  reply	other threads:[~2006-05-12 18:58 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
2006-05-12 17:36     ` Linus Torvalds
2006-05-12 17:47       ` James Bottomley
2006-05-12 18:58         ` James Bottomley [this message]
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=1147460325.3769.46.camel@mulgrave.il.steeleye.com \
    --to=james.bottomley@steeleye.com \
    --cc=axboe@suse.de \
    --cc=erik@harddisk-recovery.com \
    --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