linux-kernel - Re: linux-next: Fixes tag needs work in the device-mapper 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, 15 Jan 2019 16:12:02 -0500
From:   Mike Snitzer <snitzer@...hat.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Alasdair G Kergon <agk@...hat.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Paul Gortmaker <paul.gortmaker@...driver.com>,
        Joe Thornber <ejt@...hat.com>
Subject: Re: linux-next: Fixes tag needs work in the device-mapper tree

On Tue, Jan 15 2019 at  4:02pm -0500,
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> [I am experimenting with checking the Fixes tags in commits in linux-next.
> Please let me know if you think I am being too strict.]
> 
> Hi all,
> 
> Commit
> 
>   fc4d02aa0331 ("dm thin: fix passdown_double_checking_shared_status()")
> 
> has a malformed Fixes tag:
> 
>   Fixes: 00a0ea33b49 ("dm thin: do not queue freed thin mapping for next stage processing")
> 
> It should show at least 12 digits of the SHA1.

Fixed, thanks.
Mike