public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Andrew Morton <akpm@osdl.org>
Cc: torvalds@osdl.org, linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [GIT PATCH] USB patches for 2.6.17
Date: Thu, 22 Jun 2006 17:41:26 -0700	[thread overview]
Message-ID: <20060623004126.GA3098@suse.de> (raw)
In-Reply-To: <20060622173215.446e9de8.akpm@osdl.org>

On Thu, Jun 22, 2006 at 05:32:15PM -0700, Andrew Morton wrote:
> Greg KH <gregkh@suse.de> wrote:
> >
> > I would think it's something new too, as I did change that very line
> > that oopsed.  That's why I found it odd that I couldn't reproduce it
> > anymore.
> 
> device_destroy() looks wrong.  It alters the class->devices list outside
> its lock.
> 
> --- 25/drivers/base/core.c~device_destroy-locking-fix	Thu Jun 22 17:29:07 2006
> +++ 25-akpm/drivers/base/core.c	Thu Jun 22 17:29:34 2006
> @@ -632,14 +632,13 @@ void device_destroy(struct class *class,
>  	list_for_each_entry(dev_tmp, &class->devices, node) {
>  		if (dev_tmp->devt == devt) {
>  			dev = dev_tmp;
> +			list_del_init(&dev->node);
>  			break;
>  		}
>  	}
>  	up(&class->sem);
>  
> -	if (dev) {
> -		list_del_init(&dev->node);
> +	if (dev)
>  		device_unregister(dev);
> -	}
>  }
>  EXPORT_SYMBOL_GPL(device_destroy);
> 
> That won't be it though.

No, and that function doesn't get called for the usb endpoints, it goes
through a different path, that's the problem...  I think I've found it
now, let me reboot a bunch...

thanks,

greg k-h

  reply	other threads:[~2006-06-23  0:41 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 22:06 [GIT PATCH] USB patches for 2.6.17 Greg KH
2006-06-21 22:22 ` Linus Torvalds
2006-06-21 22:51   ` Greg KH
2006-06-22  0:51     ` Linus Torvalds
2006-06-22  1:22     ` Linus Torvalds
2006-06-22 18:18       ` Greg KH
2006-06-22 18:30         ` Greg KH
2006-06-22 18:49           ` Randy.Dunlap
2006-06-22 18:54             ` Greg KH
2006-06-23  5:52               ` Evgeniy Polyakov
2006-06-23  6:07                 ` Greg KH
2006-06-22 19:50           ` Linus Torvalds
2006-06-22 20:01             ` Sam Ravnborg
2006-06-22 20:52               ` Petr Baudis
2006-06-22 21:01               ` Linus Torvalds
2006-06-22 21:07                 ` Linus Torvalds
2006-06-22 23:11 ` Linus Torvalds
2006-06-22 23:40   ` Greg KH
2006-06-22 23:48     ` Linus Torvalds
2006-06-22 23:52       ` Greg KH
2006-06-23  0:32         ` Andrew Morton
2006-06-23  0:41           ` Greg KH [this message]
2006-06-23  0:05     ` Jeremy Fitzhardinge
2006-06-23  0:17       ` Andrew Morton
2006-06-23  0:22         ` Greg KH
2006-06-23  0:38           ` Greg KH
2006-06-23  0:56   ` Greg KH

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=20060623004126.GA3098@suse.de \
    --to=gregkh@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --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