linux-kernel - Re: [PATCH v2 01/10] objtool: Move header sync-check ealier in build

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:   Wed, 1 Apr 2020 13:44:45 +0100
From:   Julien Thierry <jthierry@...hat.com>
To:     Miroslav Benes <mbenes@...e.cz>
Cc:     linux-kernel@...r.kernel.org, jpoimboe@...hat.com,
        peterz@...radead.org, raphael.gault@....com
Subject: Re: [PATCH v2 01/10] objtool: Move header sync-check ealier in build



On 4/1/20 1:32 PM, Miroslav Benes wrote:
> On Fri, 27 Mar 2020, Julien Thierry wrote:
> 
>> Currently, the check of tools files against kernel equivalent is only
>> done after every object file has been built.
> 
>> This means one might fix
>> build issues against outdated headers without seeing a warning about
>> this.
> 
> Could you explain the above in more detail, please?
> 

I must admit that this patch is more fixing the issues I've faced while 
working on the arm64 support and sharing some kernel headers from the 
arch/arm64 tree.

The annoying part was:
- Have build errors in objtool
- Fix them
- Objtool build succeeds, but have warning about outdated headers
- Update headers
- New errors come up, potentially making obsolete the ealier fixes

So it's not really a "must have" change. But it's nice to have when 
bringing new kernel headers to objtool.

I hope this makes things clearer.

Cheers,

-- 
Julien Thierry