linux-kernel - Re: linux-next: Fixes tag needs some work in the mm-stable 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] [thread-next>] [day] [month] [year] [list]

Date:   Sun, 9 Oct 2022 18:40:15 -0700
From:   Mike Kravetz <mike.kravetz@...cle.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        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 mm-stable tree

On 10/09/22 19:35, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   bbff39cc6cbc ("hugetlb: allocate vma lock for all sharable vmas")
> 
> Fixes tag
> 
>   Fixes: "hugetlb: clean up code checking for fault/truncation races"
> 
> has these problem(s):
> 
>   - No SHA1 recognised
> 
> Maybe you meant
> 
> Fixes: fa27759af4a6 ("hugetlb: clean up code checking for fault/truncation races")

For all of these, I was under the impression that the SHA1 of commits in
Andrew's trees were not stable and could change.  That is why I purposely
did not try to add SHA1s to the tags.  Perhaps that is no longer the case
since Andrew is using git to manage patches?

I see that a pull request including these commits was already sent to
Linus.  Not sure where these are in the process, or if it may be too
late to update.  Let me know if there is anything I can do.
-- 
Mike Kravetz