All of lore.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <felipe.balbi@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: stable@vger.kernel.org, nsekhar@ti.com, rogerq@ti.com,
	januszx.dziedzic@intel.com
Subject: Re: [PATCH] usb: dwc3: gadget: delay unmap of bounced requests
Date: Mon, 10 Apr 2017 17:13:55 +0300	[thread overview]
Message-ID: <87a87oe4f0.fsf@linux.intel.com> (raw)
In-Reply-To: <20170410140440.GB31894@kroah.com>

[-- Attachment #1: Type: text/plain, Size: 1003 bytes --]

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

> On Mon, Apr 10, 2017 at 04:48:41PM +0300, Felipe Balbi wrote:
>> From: Janusz Dziedzic <januszx.dziedzic@intel.com>
>> 
>> commit d62145929992f331fdde924d5963ab49588ccc7d upstream.
>> 
>> In the case of bounced ep0 requests, we must delay DMA operation until
>> after ->complete() otherwise we might overwrite contents of req->buf.
>> 
>> This caused problems with RNDIS gadget.
>> 
>> Cc: <stable@vger.kernel.org>
>> Fixes: d62145929992 ("usb: dwc3: gadget: always unmap EP0 requests")
>> Signed-off-by: Janusz Dziedzic <januszx.dziedzic@intel.com>
>> Signed-off-by: Felipe Balbi <felipe.balbi@linux.intel.com>
>> ---
>> 
>> Note that this commit needs to be backported to all kernels where
>> d62145929992 was backported.
>
> How can you backport this patch to everywhere it was backported to
> already?  :)
>
> I think one of the git commit ids is wrong here...

hah! nice catch. I'll fix and resend

-- 
balbi

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      reply	other threads:[~2017-04-10 14:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-10 13:48 [PATCH] usb: dwc3: gadget: delay unmap of bounced requests Felipe Balbi
2017-04-10 14:04 ` Greg Kroah-Hartman
2017-04-10 14:13   ` Felipe Balbi [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=87a87oe4f0.fsf@linux.intel.com \
    --to=felipe.balbi@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=januszx.dziedzic@intel.com \
    --cc=nsekhar@ti.com \
    --cc=rogerq@ti.com \
    --cc=stable@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.