From: Andiry Xu <andiry.xu@amd.com>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Daniel Mack <zonque@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Florian Mickler <florian@mickler.org>,
Oliver Neukum <oliver@neukum.org>, <linux-usb@vger.kernel.org>,
<alsa-devel@alsa-project.org>, Takashi Iwai <tiwai@suse.de>,
Clemens Ladisch <clemens@ladisch.de>, <pedrib@gmail.com>,
William Light <wrl@illest.net>, Greg KH <greg@kroah.com>,
<linux-kernel@vger.kernel.org>,
Robert Hancock <hancockrwd@gmail.com>
Subject: Re: Allocating buffers for USB transfers (again)
Date: Thu, 11 Aug 2011 11:22:21 +0800 [thread overview]
Message-ID: <1313032941.1918.8.camel@brienza-desktop> (raw)
In-Reply-To: <20110810231552.GA7194@xanatos>
On Wed, 2011-08-10 at 16:15 -0700, Sarah Sharp wrote:
> On Wed, Aug 10, 2011 at 05:33:02PM +0200, Daniel Mack wrote:
> > On 08/10/2011 04:32 PM, Alan Stern wrote:
> > >Looking at the driver's current code, it appears that your patch
> > >does not fix the bug properly. Using discontiguous regions in the
> > >transfer buffer is perfectly okay. The real problem is later on,
> > >where you do:
> > >
> > >if (send_it) { out->number_of_packets = FRAMES_PER_URB;
> > >
> > >This should be
> > >
> > >out->number_of_packets = outframe;
> > >
> > >The way it is now, the USB stack will try to use data from all the
> > >frame descriptors, and the last few will be stale because the loop
> > >doesn't set them.
> >
> > That's actually true, even though it doesn't seem to cause any trouble.
> > I tested everything here of course, and the output URBs return back from
> > the USB stack with their length fields zeroed out, which then
> > causes the stack to send packets with zero-length fields at the end.
>
> Actually, it causes system hangs when the driver is loaded on a device
> attached to a USB 3.0 port, as Alan Stern pointed out:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=40702
>
> Please don't submit zero-length transfers. The xHCI driver just isn't
> able to handle it. Arguably, it probably should have just rejected your
> URB when it found a zero length buffer, so I'll probably be submitting a
> patch to fix that.
>
I think queue a zero-length TRB to xhci host is OK. I've not tested it,
but the issue here seems is caused by td->last_trb = NULL. Check
count_isoc_trbs_needed(), num_trbs will be 0 if the packet length is
zero and (addr & (TRB_MAS_BUFF_SIZE - 1)) is zero. We can not return
num_trbs as 0 to xhci_queue_isoc_tx(), which caused a td added to ep's
td list, while it's not actually queued to ep ring and last_trb is not
set.
In order to avoid this, we just make sure count_isoc_trbs_needed()
always return 1 or larger numbers, instead of reject the urb. Is that
feasible?
Thanks,
Andiry
next prev parent reply other threads:[~2011-08-11 3:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 11:53 Allocating buffers for USB transfers (again) Daniel Mack
2011-07-07 12:14 ` Clemens Ladisch
2011-07-07 12:29 ` Daniel Mack
2011-07-07 12:33 ` Oliver Neukum
2011-07-07 12:38 ` Daniel Mack
2011-07-07 13:08 ` Oliver Neukum
2011-07-08 15:13 ` Daniel Mack
2011-07-07 15:06 ` Alan Stern
2011-07-07 15:16 ` Florian Mickler
2011-08-10 7:51 ` Daniel Mack
2011-08-10 14:32 ` Alan Stern
2011-08-10 15:33 ` Daniel Mack
2011-08-10 18:06 ` Takashi Iwai
2011-08-10 23:15 ` Sarah Sharp
2011-08-11 0:57 ` Daniel Mack
2011-08-11 16:45 ` Sarah Sharp
2011-08-11 17:27 ` Daniel Mack
2011-08-11 18:05 ` Sarah Sharp
2011-08-11 21:39 ` Daniel Mack
2011-08-11 23:29 ` Matěj Laitl
2011-08-11 23:40 ` Daniel Mack
2011-08-11 23:50 ` Matěj Laitl
2011-08-12 1:28 ` Daniel Mack
2011-08-12 4:46 ` Sarah Sharp
2011-08-12 9:55 ` Daniel Mack
2011-08-11 3:22 ` Andiry Xu [this message]
2011-08-11 14:36 ` Alan Stern
2011-07-07 13:53 ` Johannes Stezenbach
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=1313032941.1918.8.camel@brienza-desktop \
--to=andiry.xu@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=florian@mickler.org \
--cc=greg@kroah.com \
--cc=hancockrwd@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oliver@neukum.org \
--cc=pedrib@gmail.com \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
--cc=tiwai@suse.de \
--cc=wrl@illest.net \
--cc=zonque@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox