public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Kay Sievers <kay.sievers@vrfy.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: BUG in: Driver core: convert block from raw kobjects to core devices (fwd)
Date: Mon, 5 Nov 2007 13:59:49 -0800	[thread overview]
Message-ID: <20071105215949.GA29754@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0711051644580.2800-100000@iolanthe.rowland.org>

On Mon, Nov 05, 2007 at 04:49:21PM -0500, Alan Stern wrote:
> Greg:
> 
> So what's our status?  Do you think it's worthwhile adding the 
> "drop reference to parent kobject at remove time instead of release 
> time" patch?

No.

I still need to take the time and read this thread and find the real
problem here.  The fact that the issue does not show up for other,
non-scsi block devices, makes me feel this is a scsi-specific problem
with how it deals with the driver model, but I need to take the time to
sit down and figure it out for sure.

> Also, what's the story on the updates to the USB uevent routines?  Do 
> you want separate patches from Kay and me or should we combine them 
> into a single patch?

I'll take a combined patch, as I don't think I got a signed-off for your
version, I was waiting for a "final" version.

Back to the kobject/kset cleanup/debug mess :)

thanks,

greg k-h

  reply	other threads:[~2007-11-05 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1193848942.6621.18.camel@lov.site>
2007-11-05 21:49 ` BUG in: Driver core: convert block from raw kobjects to core devices (fwd) Alan Stern
2007-11-05 21:59   ` Greg KH [this message]
2007-11-06 19:49     ` Alan Stern
2007-11-07 12:21       ` Hannes Reinecke
2007-11-07 15:54         ` Alan Stern
2007-11-07 19:36           ` Kay Sievers
2007-11-07 20:00             ` Alan Stern

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=20071105215949.GA29754@kroah.com \
    --to=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stern@rowland.harvard.edu \
    /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