linux-kernel - Re: linux-next: Fixes tag needs some work in the modules 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]

Message-ID: <Yh1sKVz4g+X0xge0@bombadil.infradead.org>
Date:   Mon, 28 Feb 2022 16:43:21 -0800
From:   Luis Chamberlain <mcgrof@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Aaron Tomlin <atomlin@...hat.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: Fixes tag needs some work in the modules tree

On Tue, Mar 01, 2022 at 11:33:33AM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   f131a1296ecf ("module: Make internal.h and decompress.c more compliant")
> 
> Fixes tag
> 
>   Fixes: f314dfea16a ("modsign: log module name in the event of an error")
> 
> has these problem(s):
> 
>   - SHA1 should be at least 12 digits long
>     This can be fixed for the future by setting core.abbrev to 12 (or
>     more) or (for git v2.11 or later) just making sure it is not set
>     (or set to "auto").

This is not that critical but I've decided to reset my tree again back
to Linus' tree as I jumped the gun in mergig this to modulex-next as it
has not been run time tested yet. So I've dumped this on modules-testing, and
once we get more testing results I'll push this to modules-next.

I can fix the commit log to have 12 digits on the SHA1 manually,
provided no other compile or run time issues are found.

  Luis