From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: christophe.leroy@c-s.fr, mpe@ellerman.id.au, stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] powerpc/kasan: Fix kasan_remap_early_shadow_ro()" failed to apply to 5.6-stable tree
Date: Wed, 15 Apr 2020 23:27:39 -0400 [thread overview]
Message-ID: <20200416032739.GG1068@sasha-vm> (raw)
In-Reply-To: <15869567019927@kroah.com>
On Wed, Apr 15, 2020 at 03:18:21PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 5.6-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 af92bad615be75c6c0d1b1c5b48178360250a187 Mon Sep 17 00:00:00 2001
>From: Christophe Leroy <christophe.leroy@c-s.fr>
>Date: Fri, 6 Mar 2020 15:09:40 +0000
>Subject: [PATCH] powerpc/kasan: Fix kasan_remap_early_shadow_ro()
>
>At the moment kasan_remap_early_shadow_ro() does nothing, because
>k_end is 0 and k_cur < 0 is always true.
>
>Change the test to k_cur != k_end, as done in
>kasan_init_shadow_page_tables()
>
>Signed-off-by: Christophe Leroy <christophe.leroy@c-s.fr>
>Fixes: cbd18991e24f ("powerpc/mm: Fix an Oops in kasan_mmu_init()")
>Cc: stable@vger.kernel.org
>Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
>Link: https://lore.kernel.org/r/4e7b56865e01569058914c991143f5961b5d4719.1583507333.git.christophe.leroy@c-s.fr
Conflict because we don't have 0b1c524caaae ("powerpc/32: refactor
pmd_offset(pud_offset(pgd_offset..."). Fixed and queued up.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-04-16 3:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-15 13:18 FAILED: patch "[PATCH] powerpc/kasan: Fix kasan_remap_early_shadow_ro()" failed to apply to 5.6-stable tree gregkh
2020-04-16 3:27 ` 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=20200416032739.GG1068@sasha-vm \
--to=sashal@kernel.org \
--cc=christophe.leroy@c-s.fr \
--cc=gregkh@linuxfoundation.org \
--cc=mpe@ellerman.id.au \
--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).