All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Boyd <swboyd@chromium.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: 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 12:41:07 -0800	[thread overview]
Message-ID: <161333526750.1254594.7267322236004310547@swboyd.mtv.corp.google.com> (raw)
In-Reply-To: <YCla7cNQxBoG2KCr@kroah.com>

Quoting Greg Kroah-Hartman (2021-02-14 09:16:29)
> 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?
> 

Ok, will do.

  reply	other threads:[~2021-02-14 20:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-07 17:05 [PATCH] lkdtm: don't move ctors to .rodata Mark Rutland
2020-12-08 21:20 ` Kees Cook
2020-12-09 14:51   ` Greg Kroah-Hartman
2021-02-11  0:36     ` 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 [this message]
2021-02-14 22:32             ` 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=161333526750.1254594.7267322236004310547@swboyd.mtv.corp.google.com \
    --to=swboyd@chromium.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 \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.