public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Erik Mouw <erik@harddisk-recovery.com>,
	Or Gerlitz <or.gerlitz@gmail.com>,
	linux-scsi@vger.kernel.org, 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: Sat, 13 May 2006 00:37:12 +0100	[thread overview]
Message-ID: <20060512233711.GW27946@ftp.linux.org.uk> (raw)
In-Reply-To: <20060512232131.GV27946@ftp.linux.org.uk>

On Sat, May 13, 2006 at 12:21:31AM +0100, Al Viro wrote:
> The problem is with disk->driverfs_dev, not disk itself.  Block layer
> has no fscking business touching it after del_gendisk() - if nothing else,
> we might have _no_ underlying object at all from the very beginning.
> 
> So anything that wants events related to partitions, let alone mounting,
> can't expect to see PHYSDEV... crap.  Moreover, it can bloody well
> get to PHYSDEV... itself *if* it wants to and if it's there.  There's
> a reason why we have that symlink in sys/block/<device> and userland can
> bloody well access it on its own.

BTW, the best option is to kill bdev_uevent() again.  Short of that,
skip PHYSDEV mess if disk doesn't have GENHD_FL_UP.

  reply	other threads:[~2006-05-12 23:37 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060511151456.GD3755@harddisk-recovery.com>
     [not found] ` <15ddcffd0605112153q57f139a1k7068e204a3eeaf1f@mail.gmail.com>
2006-05-12 17:16   ` [BUG 2.6.17-git] kmem_cache_create: duplicate cache scsi_cmd_cache 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
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 [this message]
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=20060512233711.GW27946@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --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=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