From: Greg KH <greg@kroah.com>
To: David Chang <dchang@suse.com>
Cc: "Németh Márton" <nm127@freemail.hu>,
"Matthew Wilcox" <matthew@wil.cx>,
"Max Vozeler" <max@vozeler.com>,
"Matt Mooney" <mfm@muteddisk.com>,
"Joe Perches" <joe@perches.com>,
linux-usb@vger.kernel.org, usbip-devel@lists.sourceforge.net,
devel@driverdev.osuosl.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH, RFC] USBIP protocol documentation
Date: Tue, 9 Aug 2011 07:22:56 -0700 [thread overview]
Message-ID: <20110809142256.GB1805@kroah.com> (raw)
In-Reply-To: <CAL-cBk1Kzr1Gn3YCHDpudkVSmdSWOcCo7_rpLddCUQ_3ZjP+kQ@mail.gmail.com>
On Tue, Aug 09, 2011 at 05:23:14PM +0800, David Chang wrote:
> Hi Greg,
>
> 2011/6/28 Németh Márton <nm127@freemail.hu>:
> > From: Márton Németh <nm127@freemail.hu>
> >
> > USBIP v1.0.0 protocol documentation.
> >
> > Signed-off-by: Márton Németh <nm127@freemail.hu>
> > ---
> >
> > Hi,
> >
> > I tried to document the USBIP protocol as implemented in the Linux kernel 3.0-rc2.
> >
> > The description is a preliminary draft only, it may contain mistakes. I tried
> > to document what I have understand from the source code and from the actual
> > captured network traffic when the USBIP is in action. Please review it, correct it,
> > point out the missing parts.
> >
> > During I have documented the protocol a question came into my mind: why do we
> > have two different type of package when the URB completition handler is called,
> > namely USB_RET_SUBMIT and USBIP_RET_UNLINK? As far as I can see this causes race
> > condition because for one URB the completition handler is only called once. If
> > the one URB is sent in with USB_CMD_SUBMIT and then unlinked with USB_CMD_UNLINK
> > the completition handler is called only once. In the protocol, however, we have
> > two different type of packets: USB_RET_SUBMIT and USBIP_RET_UNLINK. The status
> > field of these messages may contain anything in this case depending on the timing.
> >
> > Regards,
> >
> > Márton Németh
>
> Sorry, just one question about the usbip protocol document.
> I would like to know why didn't you apply this patch.
Because it was sent as a "RFC" (i.e. request for comments) and based on
the discussion afterward, there were lots of comments :)
If someone wants to resend it to me, without that marking, I'll be glad
to apply it.
thanks,
greg k-h
next prev parent reply other threads:[~2011-08-09 14:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-24 18:28 USBIP protocol documentation? Németh Márton
2011-05-24 18:34 ` Greg KH
2011-05-24 20:25 ` Németh Márton
2011-05-24 21:25 ` Greg KH
2011-05-25 3:12 ` matt mooney
2011-05-25 5:29 ` Németh Márton
2011-05-26 7:13 ` Németh Márton
2011-06-28 6:52 ` [PATCH, RFC] USBIP protocol documentation Németh Márton
2011-06-29 8:04 ` David Chang
2011-07-04 3:11 ` David Chang
2011-07-04 5:38 ` Németh Márton
2011-07-04 8:24 ` Matt Chen
2011-07-07 4:14 ` matt mooney
2011-07-07 6:20 ` Matt Chen
2011-07-25 4:30 ` Matt Chen
2011-06-29 23:34 ` matt mooney
[not found] ` <BANLkTi=qXgnapyrsSANJ0XZuE=kz7QgsvA@mail.gmail.com>
2011-06-30 5:56 ` Németh Márton
2011-06-30 6:54 ` Matt Chen
2011-06-30 19:38 ` Németh Márton
2011-08-09 9:23 ` David Chang
2011-08-09 14:22 ` Greg KH [this message]
2011-08-10 6:41 ` David Chang
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=20110809142256.GB1805@kroah.com \
--to=greg@kroah.com \
--cc=dchang@suse.com \
--cc=devel@driverdev.osuosl.org \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=matthew@wil.cx \
--cc=max@vozeler.com \
--cc=mfm@muteddisk.com \
--cc=nm127@freemail.hu \
--cc=usbip-devel@lists.sourceforge.net \
/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