stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: stable@vger.kernel.org
Subject: Re: io_uring stable 5.3 backports
Date: Sun, 27 Oct 2019 08:22:54 +0100	[thread overview]
Message-ID: <20191027072254.GB1755924@kroah.com> (raw)
In-Reply-To: <efc9278b-de72-40b2-9a0a-48df0c64edc1@kernel.dk>

On Sat, Oct 26, 2019 at 05:33:41PM -0600, Jens Axboe wrote:
> Hi,
> 
> For some reason I forgot to mark these stable, but they should go
> into stable. In order of applying them, they are:
> 
> bc808bced39f4e4b626c5ea8c63d5e41fce7205a
> ef03681ae8df770745978148a7fb84796ae99cba
> a1f58ba46f794b1168d1107befcf3d4b9f9fd453
> 84d55dc5b9e57b513a702fbc358e1b5489651590
> fb5ccc98782f654778cb8d96ba8a998304f9a51f
> 935d1e45908afb8853c497f2c2bbbb685dec51dc
> 498ccd9eda49117c34e0041563d0da6ac40e52b8
> 2b2ed9750fc9d040b9f6d076afcef6f00b6f1f7c

Only 2 of these patches applied to the 5.3 stable tree, are you sure you
want these all there?  If so, can you provide a backport of them all?

I already did queue up these two:
	2b2ed9750fc9 ("io_uring: fix bad inflight accounting for SETUP_IOPOLL|SETUP_SQTHREAD")
	84d55dc5b9e5 ("io_uring: Fix corrupted user_data")

thanks,

greg k-h

  reply	other threads:[~2019-10-27  7:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-26 23:33 io_uring stable 5.3 backports Jens Axboe
2019-10-27  7:22 ` Greg KH [this message]
2019-10-27  8:52 ` Sasha Levin
2019-10-27 12:01   ` Jens Axboe
2019-10-27 12:06     ` Jens Axboe
2019-10-27 13:48     ` Sasha Levin
2019-10-27 14:03       ` Jens Axboe
2019-10-27 14:24         ` Sasha Levin
2019-10-27 16:18           ` Jens Axboe
2019-10-27 18:10             ` Sasha Levin
2019-10-27 18:54               ` Jens Axboe
2019-10-27 21:55                 ` Sasha Levin

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=20191027072254.GB1755924@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=axboe@kernel.dk \
    --cc=stable@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;
as well as URLs for NNTP newsgroup(s).