linux-kernel - Re: linux-next: Fixes tag needs some work in the tip 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 for Android: free password hash cracker in your pocket

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

Message-ID: <20190118113230.3d11be0c@canb.auug.org.au>
Date:   Fri, 18 Jan 2019 11:32:30 +1100
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Thomas Gleixner <tglx@...utronix.de>
Cc:     Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: linux-next: Fixes tag needs some work in the tip tree

Hi Thomas,

On Fri, 18 Jan 2019 00:45:44 +0100 (CET) Thomas Gleixner <tglx@...utronix.de> wrote:
>
> On Fri, 18 Jan 2019, Stephen Rothwell wrote:
> > Commit
> > 
> >   a31e184e4f69 ("x86/pkeys: Properly copy pkey state at fork()")
> > 
> > Fixes tag
> > 
> >   Fixes: e8c24d3a23a ("x86/pkeys: Allocation/free syscalls")
> > 
> > has these problems:
> > 
> >   - SHA1 should be at least 12 digits long  
> 
> Sigh. I'll add that to my sanity checks, but this one has to be as is as
> it's in the middle of a series of fixes pending for linus tree.

That's OK, more of a reminder ... the abbreviated SHA1 is unique now,
but may not be in the future - of course 12 digits does not guarantee
that either.  I am told we already have some clashes using 11 digits :-(

-- 
Cheers,
Stephen Rothwell

Content of type "application/pgp-signature" skipped