From: Greg KH <gregkh@linuxfoundation.org>
To: Takashi Iwai <tiwai@suse.de>
Cc: stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] ALSA: pcm: Avoid potential races between OSS ioctls and" failed to apply to 4.14-stable tree
Date: Sun, 22 Apr 2018 09:18:37 +0200 [thread overview]
Message-ID: <20180422071837.GA18562@kroah.com> (raw)
In-Reply-To: <s5hd0ytpxh4.wl-tiwai@suse.de>
On Fri, Apr 20, 2018 at 08:02:47PM +0200, Takashi Iwai wrote:
> On Fri, 20 Apr 2018 18:08:28 +0200,
> <gregkh@linuxfoundation.org> wrote:
> >
> >
> > The patch below does not apply to the 4.14-stable tree.
> > If someone wants it applied there, or to any other stable or longterm
> > tree, then please email the backport, including the original git commit
> > id to <stable@vger.kernel.org>.
>
> It's because of one missing prerequisite commit.
>
> Could you cherry-pick the following commit at first?
> c64ed5dd9feba193c76eb460b451225ac2a0d87b
> ALSA: pcm: Use ERESTARTSYS instead of EINTR in OSS emulation
>
> Then the rest commits should be cleanly applicable, at least to
> 4.14.y:
> 02a5d6925cd34c3b774bdb8eefb057c40a30e870
> ALSA: pcm: Avoid potential races between OSS ioctls and read/write
> 40cab6e88cb0b6c56d3f30b7491a20e803f948f6
> ALSA: pcm: Return -EBUSY for OSS ioctls changing busy streams
> f6d297df4dd47ef949540e4a201230d0c5308325
> ALSA: pcm: Fix mutex unbalance in OSS emulation ioctls
> e15dc99dbb9cf99f6432e8e3c0b3a8f7a3403a86
> ALSA: pcm: Fix endless loop for XRUN recovery in OSS emulation
Thanks, that worked.
greg k-h
prev parent reply other threads:[~2018-04-22 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-20 16:08 FAILED: patch "[PATCH] ALSA: pcm: Avoid potential races between OSS ioctls and" failed to apply to 4.14-stable tree gregkh
2018-04-20 18:02 ` Takashi Iwai
2018-04-22 7:18 ` Greg KH [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=20180422071837.GA18562@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=stable@vger.kernel.org \
--cc=tiwai@suse.de \
/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.