From: Greg KH <gregkh@linuxfoundation.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: David.Laight@aculab.com, akpm@linux-foundation.org,
arnd@arndb.de, axboe@kernel.dk, dave@stgolabs.net,
deepa.kernel@gmail.com, e@80x24.org, ebiederm@xmission.com,
jbaron@akamai.com, mtk.manpages@gmail.com,
stable@vger.kernel.org, tglx@linutronix.de,
torvalds@linux-foundation.org, viro@zeniv.linux.org.uk
Subject: Re: FAILED: patch "[PATCH] signal: remove the wrong signal_pending() check in" failed to apply to 5.1-stable tree
Date: Wed, 3 Jul 2019 14:13:25 +0200 [thread overview]
Message-ID: <20190703121325.GC7784@kroah.com> (raw)
In-Reply-To: <20190702172802.GA11460@redhat.com>
On Tue, Jul 02, 2019 at 07:28:02PM +0200, Oleg Nesterov wrote:
> On 07/01, gregkh@linuxfoundation.org wrote:
> >
> > The patch below does not apply to the 5.1-stable tree.
> ...
> > ------------------ original commit in Linus's tree ------------------
> >
> > From 97abc889ee296faf95ca0e978340fb7b942a3e32 Mon Sep 17 00:00:00 2001
> > From: Oleg Nesterov <oleg@redhat.com>
> > Date: Fri, 28 Jun 2019 12:06:50 -0700
> > Subject: [PATCH] signal: remove the wrong signal_pending() check in
> > restore_user_sigmask()
>
> because 5.1 doesn't have fdb288a679cd ("io_uring: use wait_event_interruptible
> for cq_wait conditional wait").
>
> Please see the updated patch below. Compile tested...
Thanks for this, now queued up.
greg k-h
prev parent reply other threads:[~2019-07-03 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 14:17 FAILED: patch "[PATCH] signal: remove the wrong signal_pending() check in" failed to apply to 5.1-stable tree gregkh
2019-07-02 17:28 ` Oleg Nesterov
2019-07-03 12:13 ` 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=20190703121325.GC7784@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=David.Laight@aculab.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=dave@stgolabs.net \
--cc=deepa.kernel@gmail.com \
--cc=e@80x24.org \
--cc=ebiederm@xmission.com \
--cc=jbaron@akamai.com \
--cc=mtk.manpages@gmail.com \
--cc=oleg@redhat.com \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).