From: Gerd Hoffmann <kraxel@redhat.com>
To: mars@linux.vnet.ibm.com
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH V2] Fix parse of usb device description with multiple configurations
Date: Tue, 13 Dec 2011 14:34:56 +0100 [thread overview]
Message-ID: <4EE75480.5080003@redhat.com> (raw)
In-Reply-To: <1323739340-11364-1-git-send-email-mars@linux.vnet.ibm.com>
On 12/13/11 02:22, mars@linux.vnet.ibm.com wrote:
> When testing ipod on QEMU by He Jie Xu<xuhj@linux.vnet.ibm.com>,qemu made a assertion.
> We found that the ipod with 2 configurations,and the usb-linux did not parse the descriptor correctly.
> The descr_len returned is the total length of the all configurations,not one configuration.
> The older version will through the other configurations instead of skip,continue parsing the descriptor of interfaces/endpoints in other configurations,then went wrong.
>
> This patch will put the configuration descriptor parse in loop outside and dispel the other configurations not requested.
Patch added to usb patch queue.
thanks,
Gerd
prev parent reply other threads:[~2011-12-13 13:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-13 1:22 [Qemu-devel] [PATCH V2] Fix parse of usb device description with multiple configurations mars
2011-12-13 13:34 ` Gerd Hoffmann [this message]
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=4EE75480.5080003@redhat.com \
--to=kraxel@redhat.com \
--cc=mars@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).