From: Nathan Chancellor <natechancellor@gmail.com>
To: Sasha Levin <sashal@kernel.org>
Cc: Nick Desaulniers <ndesaulniers@google.com>,
gregkh@linuxfoundation.org, clang-built-linux@googlegroups.com,
stable@vger.kernel.org
Subject: Re: [PATCH v3] lkdtm: support llvm-objcopy
Date: Thu, 16 May 2019 21:06:13 -0700 [thread overview]
Message-ID: <20190517040613.GA13981@archlinux-epyc> (raw)
In-Reply-To: <20190517001002.D1A262084A@mail.kernel.org>
On Fri, May 17, 2019 at 12:10:02AM +0000, Sasha Levin wrote:
> Hi,
>
> [This is an automated email]
>
> This commit has been processed because it contains a -stable tag.
> The stable tag indicates that it's relevant for the following trees: all
Nick, the stable tag should probably specify 4.8+ since the commit it
fixes came in during 4.8-rc1.
Cc: stable@vger.kernel.org # 4.8+
Might also help to add:
Fixes: 9a49a528dcf3 ("lkdtm: add function for testing .rodata section")
>
> The bot has tested the following trees: v5.1.2, v5.0.16, v4.19.43, v4.14.119, v4.9.176, v4.4.179, v3.18.140.
>
> v5.1.2: Build OK!
> v5.0.16: Build OK!
> v4.19.43: Build OK!
> v4.14.119: Failed to apply! Possible dependencies:
> 039a1c42058d ("lkdtm: Relocate code to subdirectory")
However, it will still need a manual backport because of the lack of
this commit. I've attached the current patch backported for reference,
the git am flags '-3 -p4 --directory=drivers/misc' help get it proper
then the conflict is rather easy to resolve.
Thanks,
Nathan
next prev parent reply other threads:[~2019-05-17 4:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-13 22:21 [PATCH] lkdtm: support llvm-objcopy Nick Desaulniers
2019-05-13 22:26 ` Nick Desaulniers
2019-05-13 23:04 ` Kees Cook
2019-05-13 23:29 ` Nathan Chancellor
2019-05-13 23:38 ` Jordan Rupprecht
2019-05-13 23:47 ` Nathan Chancellor
2019-05-13 23:50 ` Nick Desaulniers
2019-05-14 18:10 ` Kees Cook
2019-05-14 20:24 ` Nick Desaulniers
2019-05-15 16:42 ` Kees Cook
2019-05-15 17:37 ` Nick Desaulniers
2019-05-15 18:12 ` [PATCH v2] " Nick Desaulniers
2019-05-15 18:19 ` Nathan Chancellor
2019-05-15 18:24 ` [PATCH v3] " Nick Desaulniers
[not found] ` <20190517001002.D1A262084A@mail.kernel.org>
2019-05-17 4:06 ` Nathan Chancellor [this message]
2019-05-17 4:09 ` Nathan Chancellor
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=20190517040613.GA13981@archlinux-epyc \
--to=natechancellor@gmail.com \
--cc=clang-built-linux@googlegroups.com \
--cc=gregkh@linuxfoundation.org \
--cc=ndesaulniers@google.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 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.