linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@kernel.org>
To: "Ardelean\, Alexandru" <alexandru.Ardelean@analog.com>,
	"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: "gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"mina86\@mina86.com" <mina86@mina86.com>,
	"lars\@metafoo.de" <lars@metafoo.de>
Subject: Re: [PATCH] usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags
Date: Thu, 16 Jan 2020 15:04:48 +0200	[thread overview]
Message-ID: <87imlb5z7z.fsf@kernel.org> (raw)
In-Reply-To: <f3f8e2a6480da78ba23ddedb68beee71f47e178f.camel@analog.com>

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


Hi,

"Ardelean, Alexandru" <alexandru.Ardelean@analog.com> writes:

> On Wed, 2019-11-06 at 14:02 +0200, Alexandru Ardelean wrote:
>> From: Lars-Peter Clausen <lars@metafoo.de>
>> 
>> ffs_aio_cancel() can be called from both interrupt and thread context.
>> Make
>> sure that the current IRQ state is saved and restored by using
>> spin_{un,}lock_irq{save,restore}().
>> 
>> Otherwise undefined behavior might occur.
>
> Hey,
>
> This is a patch-ping.

Please read:

https://lore.kernel.org/linux-usb/875zhd6pw0.fsf@kernel.org/T/#u

We're gonna need a resend, sorry

-- 
balbi

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

  reply	other threads:[~2020-01-16 13:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-06 12:02 [PATCH] usb: gadget: ffs: ffs_aio_cancel(): Save/restore IRQ flags Alexandru Ardelean
2020-01-16 11:13 ` Ardelean, Alexandru
2020-01-16 13:04   ` Felipe Balbi [this message]
2020-01-16 13:05     ` Ardelean, Alexandru
2020-01-16 13:29 ` [PATCH][RESEND] " Alexandru Ardelean
2020-01-18 13:18   ` Michał Nazarewicz

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=87imlb5z7z.fsf@kernel.org \
    --to=balbi@kernel.org \
    --cc=alexandru.Ardelean@analog.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mina86@mina86.com \
    /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).