From: Greg KH <gregkh@linuxfoundation.org>
To: Jillian Donahue <jilliandonahue58@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] f_midi_complete to call tasklet_hi_schedule
Date: Fri, 7 Feb 2025 10:35:16 +0100 [thread overview]
Message-ID: <2025020708-manned-antidote-7d57@gregkh> (raw)
In-Reply-To: <CAArt=Lib_PiR1z07hb1E3tqq-PG=KVKU9CZP3cPsQE5ciokLVw@mail.gmail.com>
On Thu, Feb 06, 2025 at 12:32:14PM -0700, Jillian Donahue wrote:
> >From 9cb2628740d9f55f6f3faa5cce2de5eb8590f434 Mon Sep 17 00:00:00 2001
> From: Jill Donahue <jilliandonahue58@gmail.com>
> Date: Thu, 6 Feb 2025 10:18:05 -0700
> Subject: [PATCH] f_midi_complete to call tasklet_hi_schedule
This all shouldn't be in the body of the email, please do not use web
email clients. The kernel documentation should show you how to use git
send-email or other tools.
>
> When using USB MIDI, a lock is attempted to be acquired twice through a
> re-entrant call to f_midi_transmit, causing a deadlock.
>
> Fix it by using tasklet_hi_schedule() to schedule the inner
> f_midi_transmit() via a tasklet from the completion handler.
>
> Link: https://lore.kernel.org/all/CAArt=LjxU0fUZOj06X+5tkeGT+6RbXzpWg1h4t4Fwa_KGVAX6g@mail.gmail.com/
>
> Fixes: d5daf49b58661 ("USB: gadget: midi: add midi function driver")
No Cc: stable?
No blank line between Link: and Fixes: please
> Signed-off-by: Jill Donahue <jilliandonahue58@gmail.com>
> ---
> drivers/usb/gadget/function/f_midi.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
And this is a v2 patch, right?
>
> diff --git a/drivers/usb/gadget/function/f_midi.c
> b/drivers/usb/gadget/function/f_midi.c
> index 837fcdfa3..37d438e5d 100644
> --- a/drivers/usb/gadget/function/f_midi.c
> +++ b/drivers/usb/gadget/function/f_midi.c
> @@ -283,7 +283,7 @@ f_midi_complete(struct usb_ep *ep, struct usb_request *req)
> /* Our transmit completed. See if there's more to go.
> * f_midi_transmit eats req, don't queue it again. */
> req->length = 0;
> - f_midi_transmit(midi);
> + tasklet_hi_schedule(&midi->tasklet);
> return;
> }
Your whitespace is all damaged and this can't be applied :(
thanks,
greg k-h
next prev parent reply other threads:[~2025-02-07 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 19:32 [PATCH] f_midi_complete to call tasklet_hi_schedule Jillian Donahue
2025-02-07 9:35 ` Greg KH [this message]
2025-02-07 16:10 ` Jillian Donahue
2025-02-07 16:32 ` Greg KH
2025-02-07 16:36 ` Sebastian Andrzej Siewior
-- strict thread matches above, loose matches on Subject: below --
2025-02-06 19:23 Jillian Donahue
2025-02-06 19:36 ` Jillian Donahue
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=2025020708-manned-antidote-7d57@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jilliandonahue58@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.