public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: linux-usb-devel@lists.sourceforge.net, warren@togami.com,
	linux-scsi@vger.kernel.org
Subject: Re: Usb in 2.6 breaks proc
Date: Thu, 7 Aug 2003 16:49:32 -0700	[thread overview]
Message-ID: <20030807234932.GA13780@kroah.com> (raw)
In-Reply-To: <20030807191740.C27716@devserv.devel.redhat.com>

On Thu, Aug 07, 2003 at 07:17:40PM -0400, Pete Zaitcev wrote:
> Greg, Matt & folks:
> 
> There was a tangential report from one of our users that /proc
> seems to get corrupt when usb-storage is rmmod-ed and inserted again.
> 
> Kernel 2.6.0-0.test2.1.29 (Arjan's -test2 based RPM).
> 
> Problem looks like this:
> 
> [root@laptop scsi]# pwd
> /proc/scsi
> [root@laptop scsi]# find
> .
> ./usb-storage
> ./usb-storage/2
> ./usb-storage
> ./usb-storage/2
> ./device_info
> ./scsi

Ouch, could this be a scsi issue?  I know a bunch of patches are pending
to get into Linus's tree with regards to scsi reference counting and
such.

thanks,

greg k-h


-------------------------------------------------------
This SF.Net email sponsored by: Free pre-built ASP.NET sites including
Data Reports, E-commerce, Portals, and Forums are available now.
Download today and enter to win an XBOX or Visual Studio .NET.
http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel

       reply	other threads:[~2003-08-07 23:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030807191740.C27716@devserv.devel.redhat.com>
2003-08-07 23:49 ` Greg KH [this message]
2003-08-08  0:10   ` [linux-usb-devel] Usb in 2.6 breaks proc Matthew Dharm

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=20030807234932.GA13780@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=warren@togami.com \
    --cc=zaitcev@redhat.com \
    /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