linux-hardening.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kees Cook <keescook@chromium.org>
Cc: 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 18:02:09 +0200	[thread overview]
Message-ID: <YTowAX7szcAP7ItU@kroah.com> (raw)
In-Reply-To: <202109090848.129A49E8BD@keescook>

On Thu, Sep 09, 2021 at 08:49:57AM -0700, Kees Cook wrote:
> On Wed, Sep 01, 2021 at 04:34:06PM -0700, Kees Cook wrote:
> > Using generated/compile.h triggered a full LKDTM rebuild with every
> > build. Avoid this by using the exported strings instead.
> > 
> > Fixes: b8661450bc7f ("lkdtm: Add kernel version to failure hints")
> > Signed-off-by: Kees Cook <keescook@chromium.org>
> 
> Hi Greg,
> 
> Your bot said "please wait, the merge window is open", but it'd be really
> nice to get this into -rc1 to avoid annoying people doing rebuilds...
> 
> :)

I'm not supposed to be adding new patches to my tree during this period
of time in the merge window.

I can't see a rebuild locally here without this patch attached, so how
much of a problem is it right now?

And isn't -rc2 ok?

thanks,

greg k-h

  reply	other threads:[~2021-09-09 16:02 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 [this message]
2021-09-09 16:08     ` Mark Brown
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=YTowAX7szcAP7ItU@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=arnd@arndb.de \
    --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).