From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Marco Elver <elver@google.com>
Cc: stable <stable@vger.kernel.org>, Sasha Levin <sashal@kernel.org>,
Alexander Potapenko <glider@google.com>,
kasan-dev <kasan-dev@googlegroups.com>
Subject: Re: [5.12.y] kfence: use TASK_IDLE when awaiting allocation
Date: Tue, 8 Jun 2021 15:21:10 +0200 [thread overview]
Message-ID: <YL9uxro0BJgLXYTZ@kroah.com> (raw)
In-Reply-To: <CANpmjNObVfB6AREacptbMTikzbFfGuuL49jZqPSOTUjAExyp+g@mail.gmail.com>
On Mon, Jun 07, 2021 at 04:23:34PM +0200, Marco Elver wrote:
> Dear stable maintainers,
>
> The patch "kfence: use TASK_IDLE when awaiting allocation" has landed
> in mainline as 8fd0e995cc7b, however, does not apply cleanly to 5.12.y
> due to a prerequisite patch missing.
>
> My recommendation is to cherry-pick the following 2 commits to 5.12.y
> (rather than rebase 8fd0e995cc7b on top of 5.12.y):
>
> 37c9284f6932 kfence: maximize allocation wait timeout duration
> 8fd0e995cc7b kfence: use TASK_IDLE when awaiting allocation
Thanks, that worked!
greg k-h
prev parent reply other threads:[~2021-06-08 13:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-21 8:32 [PATCH] kfence: use TASK_IDLE when awaiting allocation Marco Elver
2021-05-21 9:39 ` David Laight
2021-05-21 9:47 ` Marco Elver
2021-05-21 10:15 ` David Laight
[not found] ` <20210521093715.1813-1-hdanton@sina.com>
2021-05-21 11:17 ` Marco Elver
2021-06-07 14:23 ` [5.12.y] " Marco Elver
2021-06-08 13:21 ` Greg Kroah-Hartman [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=YL9uxro0BJgLXYTZ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=elver@google.com \
--cc=glider@google.com \
--cc=kasan-dev@googlegroups.com \
--cc=sashal@kernel.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).