stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: axboe@kernel.dk, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] io-wq: add support for inheriting ->fs" failed to apply to 5.5-stable tree
Date: Tue, 18 Feb 2020 12:11:37 -0500	[thread overview]
Message-ID: <20200218171137.GS1734@sasha-vm> (raw)
In-Reply-To: <1581966726127197@kroah.com>

On Mon, Feb 17, 2020 at 08:12:06PM +0100, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.5-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>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 9392a27d88b9707145d713654eb26f0c29789e50 Mon Sep 17 00:00:00 2001
>From: Jens Axboe <axboe@kernel.dk>
>Date: Thu, 6 Feb 2020 21:42:51 -0700
>Subject: [PATCH] io-wq: add support for inheriting ->fs
>
>Some work items need this for relative path lookup, make it available
>like the other inherited credentials/mm/etc.
>
>Cc: stable@vger.kernel.org # 5.3+
>Signed-off-by: Jens Axboe <axboe@kernel.dk>

It needed some context adjustment going back to 5.5 due to cccf0ee83455
("io_uring/io-wq: don't use static creds/mm assignments").

Do we actually need this on 5.4? I thought io-wq was a 5.5 thing?

-- 
Thanks,
Sasha

      reply	other threads:[~2020-02-18 17:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-17 19:12 FAILED: patch "[PATCH] io-wq: add support for inheriting ->fs" failed to apply to 5.5-stable tree gregkh
2020-02-18 17:11 ` Sasha Levin [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=20200218171137.GS1734@sasha-vm \
    --to=sashal@kernel.org \
    --cc=axboe@kernel.dk \
    --cc=gregkh@linuxfoundation.org \
    --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).