Linux USB
 help / color / mirror / Atom feed
From: dean@sensoray.com
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-dev@sensoray.com, balbi@kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: gadget: function fs req_match endpoint address fix
Date: Tue, 10 Oct 2023 10:02:22 -0500	[thread overview]
Message-ID: <17afa339f888408c3d49e5b4adb19c06@sensoray.com> (raw)
In-Reply-To: <2023101025-tavern-properly-3114@gregkh>

On 2023-10-10 01:00, Greg KH wrote:
> On Mon, Oct 09, 2023 at 03:06:56PM -0700, linux-dev@sensoray.com wrote:
>> From: Dean Anderson <linux-dev@sensoray.com>
>> 
>> Fixes f_fs.c handling USB_RECIP_ENDPOINT request types incorrectly for
>> endpoints not belonging to it. f_fs.c needs to distinguish between IN
>> and OUT endpoints, not just the endpoint number. Otherwise, f_fs may
>> handle endpoints belonging to other functions. This occurs in the
>> gadget/composite.c composite_setup function in the req_match callback.
>> 
>> Signed-off-by: Dean Anderson <linux-dev@sensoray.com>
>> 
>> ---
>>  drivers/usb/gadget/function/f_fs.c | 14 ++++++++++----
>>  1 file changed, 10 insertions(+), 4 deletions(-)
> 
> What commit id does this fix?

8a749fd1a8720d4619c91c8b6e7528c0a355c0aa

"git log"

commit df91c8a9c05098f06ad2dd5bf0d9342e80a9eb22 (HEAD -> v6.6-rc4)
Author: Dean A <dean@sensoray.com>
Date:   Mon Oct 9 15:04:19 2023 -0700

     usb: gadget: function fs req_match endpoint address fix

commit 8a749fd1a8720d4619c91c8b6e7528c0a355c0aa (tag: v6.6-rc4)
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Sun Oct 1 14:15:13 2023 -0700

     Linux 6.6-rc4


      reply	other threads:[~2023-10-10 15:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09 22:06 [PATCH] usb: gadget: function fs req_match endpoint address fix linux-dev
2023-10-10  6:00 ` Greg KH
2023-10-10 15:02   ` dean [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=17afa339f888408c3d49e5b4adb19c06@sensoray.com \
    --to=dean@sensoray.com \
    --cc=balbi@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-dev@sensoray.com \
    --cc=linux-usb@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox