From: Patrick Mansfield <patmans@us.ibm.com>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: "goggin, edward" <egoggin@emc.com>,
'Rolf Eike Beer' <eike-kernel@sf-tec.de>,
'Andrew Morton' <akpm@osdl.org>,
Masanari Iida <standby24x7@gmail.com>,
linux-kernel@vger.kernel.org,
linux-usb-devel@lists.sourceforge.net,
linux-scsi@vger.kernel.org
Subject: Re: oops with USB Storage on 2.6.14
Date: Tue, 8 Nov 2005 13:33:06 -0800 [thread overview]
Message-ID: <20051108213306.GA25219@us.ibm.com> (raw)
In-Reply-To: <1131484123.3270.36.camel@mulgrave>
On Tue, Nov 08, 2005 at 04:08:43PM -0500, James Bottomley wrote:
> On Tue, 2005-11-08 at 15:02 -0500, goggin, edward wrote:
> > Thanks! Here's a better one.
>
> It's line wrapped, but I fixed that up.
What code path triggered this?
I mean we get a ref to the sdev in the upper level driver opens, scan, and
sd flush. So where are we not getting a ref?
Shouldn't the get be done at a higher level?
-- Patrick Mansfield
next prev parent reply other threads:[~2005-11-08 21:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 20:02 oops with USB Storage on 2.6.14 goggin, edward
2005-11-08 21:08 ` James Bottomley
2005-11-08 21:33 ` Patrick Mansfield [this message]
2005-11-08 21:45 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2005-12-07 3:29 goggin, edward
2005-12-07 3:29 ` goggin, edward
2005-11-08 18:02 goggin, edward
2005-11-08 18:02 ` goggin, edward
2005-11-08 16:24 goggin, edward
2005-11-08 16:38 ` Rolf Eike Beer
2005-11-08 17:01 ` James Bottomley
2005-11-08 17:01 ` James Bottomley
2005-10-29 12:11 Masanari Iida
2005-10-29 15:04 ` Gene Heskett
2005-10-30 19:03 ` Andrew Morton
2005-10-31 0:41 ` Masanari Iida
2005-10-31 1:02 ` Andrew Morton
2005-11-08 4:40 ` Andrew Morton
2005-11-08 15:01 ` Masanari Iida
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=20051108213306.GA25219@us.ibm.com \
--to=patmans@us.ibm.com \
--cc=James.Bottomley@SteelEye.com \
--cc=akpm@osdl.org \
--cc=egoggin@emc.com \
--cc=eike-kernel@sf-tec.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=standby24x7@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.