linux-kernel - Re: linux-next: build warnings after merge of the tomoyo tree

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] [day] [month] [year] [list]

Date:   Tue, 31 May 2022 09:45:47 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     Tetsuo Handa <penguin-kernel@...ove.sakura.ne.jp>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build warnings after merge of the tomoyo tree

On Mon, May 30, 2022 at 9:32 PM Tetsuo Handa
<penguin-kernel@...ove.sakura.ne.jp> wrote:
>
> Yes, currently there are many matches when building all modules.
> But do developers build all modules?

They had better. Every time you change a core header file, you'd
better check it. And the minimum check is "build as much as you can on
your primary architecture", which is usually something like
'allmodconfig'.

> Hmm, an important part which was missing in commit 771c035372a036f8 ("deprecate
> the '__deprecated' attribute warnings entirely and for good") is that Linus
> builds all modules and reads all messages during the build?

Indeed. I do an 'allmodconfig' build between every single pull  I do
(except when traveling - it gets too painful on a laptop), and often
do a couple of other builds too (ie I have my own "machine config"
that I also do).

And yeah, I will complain if that build is not quiet. The standard
kernel build needs to be _clean_, because that's the only way you
notice when new problems happen.

                 Linus