linux-kernel - Re: [GIT PULL] kbuild misc fixes for v4.2-rc1

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]

Date:	Thu, 2 Jul 2015 15:25:07 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Michal Marek <mmarek@...e.cz>
Cc:	Andi Kleen <ak@...ux.intel.com>, andrej.skvortzov@...il.com,
	arnaud.patard@...-net.org, Borislav Petkov <bp@...e.de>,
	dmitry.kalinkin@...il.com, Florian Fainelli <f.fainelli@...il.com>,
	fabio.estevam@...escale.com, Jim Davis <jim.epost@...il.com>,
	riku.voipio@...aro.org,
	Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] kbuild misc fixes for v4.2-rc1

So with all these changes to the build system fro 4.2, I'm *still*
getting that annoying

   X.509 certificate list changed

issue. Which apparently people don't normally see, because it does to
stdout rather than to stderr, so it's hidden by all the other random
build output.

Making it show more information gives me

   X.509 certificate list changed to "signing_key.x509" from
"./signing_key.x509"

so it's still that "./" issue.

This is *trivial* to reproduce for me using

    git clean -dqfx
    make oldconfig
    make -j16
    make -j16

where that second "make" invocation will do it.

Not only is that "./" wrong, but the whole rule to check equality is
bad because the certificate list is still generated the wrong way
around, and then randomly deleted without proper rules for it.

I sent a patch to do it right (using filechk), but it apparently never
got merged? Instead, we continue to have that racy "remove the
.x509.list file at a random time" thing.

Do I need to fish out my patch and apply it directly? I hate just
bypassing the maintainership chain for stupid things like this, but
this has been pending for way too long. At least that fixes the
re-generation of that file, even if it doesn't fix the problem with
the spurious extra ./ at the head.

                  Linus
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/