linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: Peter Chen <hzpeterchen@gmail.com>, "Du\,
	Changbin" <changbin.du@intel.com>
Cc: "balbi\@ti.com" <balbi@ti.com>,
	"gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"viro\@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"r.baldyga\@samsung.com" <r.baldyga@samsung.com>,
	"rui.silva\@linaro.org" <rui.silva@linaro.org>,
	"k.opasiak\@samsung.com" <k.opasiak@samsung.com>,
	"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: f_fs: avoid race condition with ffs_epfile_io_complete
Date: Tue, 05 Jan 2016 13:45:06 +0100	[thread overview]
Message-ID: <xa1t37ucure5.fsf@mina86.com> (raw)
In-Reply-To: <20160105054906.GB29244@shlinux2>

On Tue, Jan 05 2016, Peter Chen wrote:
> Why -EINTR, the kernel-doc said it should return -ECONNRESET for
> active request, see include/linux/usb/gadget.h.

Because EINTR is what read returns to the user if the operation has been
interrupted by a signal, see ‘man 2 read’:

       EINTR The call was interrupted by a signal before any data was
       read; see signal(7).


-- 
Best regards,                                         _     _
.o. | Liege of Serenely Enlightened Majesty of      o' \,=./ `o
..o | Computer Science,  ミハウ “mina86” ナザレヴイツ  (o o)
ooo +--<mpn@google.com>--<xmpp:mina86@jabber.org>--ooO--(_)--Ooo--

      parent reply	other threads:[~2016-01-05 12:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-29  6:36 [PATCH] usb: f_fs: avoid race condition with ffs_epfile_io_complete changbin.du
2016-01-04 20:33 ` Michal Nazarewicz
2016-01-05  3:32 ` Peter Chen
2016-01-05  4:09   ` Du, Changbin
2016-01-05  5:49     ` Peter Chen
2016-01-05  6:22       ` Du, Changbin
2016-01-05 12:45       ` Michal Nazarewicz [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=xa1t37ucure5.fsf@mina86.com \
    --to=mina86@mina86.com \
    --cc=balbi@ti.com \
    --cc=changbin.du@intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hzpeterchen@gmail.com \
    --cc=k.opasiak@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=r.baldyga@samsung.com \
    --cc=rui.silva@linaro.org \
    --cc=viro@zeniv.linux.org.uk \
    /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).