From: Mark Brown <broonie@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Kees Cook <keescook@chromium.org>, Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Re: [PATCH] lkdtm: Use init_uts_ns.name instead of macros
Date: Thu, 9 Sep 2021 17:08:59 +0100 [thread overview]
Message-ID: <20210909160859.GE5176@sirena.org.uk> (raw)
In-Reply-To: <YTowAX7szcAP7ItU@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
On Thu, Sep 09, 2021 at 06:02:09PM +0200, Greg Kroah-Hartman wrote:
> I can't see a rebuild locally here without this patch attached, so how
> much of a problem is it right now?
It's triggering for me all the time here FWIW.
> And isn't -rc2 ok?
Lots of trees base off -rc1 so unless people change their workflow to
merge up -rc2 it'll impact submitters.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-09-09 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 23:34 [PATCH] lkdtm: Use init_uts_ns.name instead of macros Kees Cook
2021-09-09 15:49 ` Kees Cook
2021-09-09 16:02 ` Greg Kroah-Hartman
2021-09-09 16:08 ` Mark Brown [this message]
2021-09-09 17:26 ` Kees Cook
2021-09-10 15:10 ` Greg Kroah-Hartman
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=20210909160859.GE5176@sirena.org.uk \
--to=broonie@kernel.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@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).