From: Sasha Levin <sashal@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Stephen Boyd <swboyd@chromium.org>,
Kees Cook <keescook@chromium.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
stable@vger.kernel.org
Subject: Re: [PATCH] lkdtm: don't move ctors to .rodata
Date: Sun, 14 Feb 2021 17:32:57 -0500 [thread overview]
Message-ID: <20210214223257.GA2858@sasha-vm> (raw)
In-Reply-To: <YCla7cNQxBoG2KCr@kroah.com>
On Sun, Feb 14, 2021 at 06:16:29PM +0100, Greg Kroah-Hartman wrote:
>On Thu, Feb 11, 2021 at 10:53:10AM -0800, Stephen Boyd wrote:
>> Sorry for the confusion. Can commit 655389666643 ("vmlinux.lds.h: Create
>> section for protection against instrumentation") and commit 3f618ab33234
>> ("lkdtm: don't move ctors to .rodata") be backported to 5.4.y and only
>> commit 3f618ab3323407ee4c6a6734a37eb6e9663ebfb9 be backported to 5.10.y?
>
>655389666643 ("vmlinux.lds.h: Create section for protection against
>instrumentation") does not apply cleanly to 5.4.y, so can you provide a
>working backport for both of those patches to 5.4.y that you have
>tested?
It was due to a backport of eff8728fe698 ("vmlinux.lds.h: Add PGO and
AutoFDO input sections"). Taking 655389666643 and 3f618ab33234 converged
us back with Linus's tree as eff8728fe698 worked around not having those
in 5.4.
I've fixed it up and queued both of those patches.
--
Thanks,
Sasha
prev parent reply other threads:[~2021-02-14 22:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20201207170533.10738-1-mark.rutland@arm.com>
[not found] ` <202012081319.D5827CF@keescook>
[not found] ` <X9DkdTGAiAEfUvm5@kroah.com>
2021-02-11 0:36 ` [PATCH] lkdtm: don't move ctors to .rodata Stephen Boyd
2021-02-11 14:23 ` Greg Kroah-Hartman
2021-02-11 18:53 ` Stephen Boyd
2021-02-14 17:16 ` Greg Kroah-Hartman
2021-02-14 20:41 ` Stephen Boyd
2021-02-14 22:32 ` 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=20210214223257.GA2858@sasha-vm \
--to=sashal@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=stable@vger.kernel.org \
--cc=swboyd@chromium.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).