linux-kernel - Re: [PATCH] lkdtm: Use init_uts

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <202109091025.A70080F@keescook>
Date:   Thu, 9 Sep 2021 10:26:18 -0700
From:   Kees Cook <keescook@...omium.org>
To:     Mark Brown <broonie@...nel.org>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Arnd Bergmann <arnd@...db.de>, linux-kernel@...r.kernel.org,
        linux-hardening@...r.kernel.org
Subject: Re: [PATCH] lkdtm: Use init_uts_ns.name instead of macros

On Thu, Sep 09, 2021 at 05:08:59PM +0100, Mark Brown wrote:
> 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.

Right, if you have CONFIG_LKDTM!=n it'll show up (e.g. with an
all*config build).

> > 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.

Right, that's why I was suggesting it.

-- 
Kees Cook