[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1605131026560.2049-100000@iolanthe.rowland.org>
Date: Fri, 13 May 2016 10:29:36 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Felipe Balbi <felipe.balbi@...ux.intel.com>
cc: "Du, Changbin" <changbin.du@...el.com>,
Al Viro <viro@...iv.linux.org.uk>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"mina86@...a86.com" <mina86@...a86.com>,
"rui.silva@...aro.org" <rui.silva@...aro.org>,
"k.opasiak@...sung.com" <k.opasiak@...sung.com>,
"lars@...afoo.de" <lars@...afoo.de>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] usb: gadget: f_fs: report error if excess data received
On Fri, 13 May 2016, Felipe Balbi wrote:
> We deliver to userspace the part userspace requested, right? So that's
> okay. The USB details WRT e.g. babble or host trying to send more data
> than expected, needs to be handled within the kernel.
The point is that you don't know whether the host sent more data than
expected. All you know is that the host sent more data than the user
asked the kernel for -- but maybe the user didn't ask for all the data
that he expected. Maybe the user wanted to retrieve the full set of
data using two read() system calls.
Alan Stern
Powered by blists - more mailing lists