linux-kernel - Re: linux-next: Fixes tag needs some work in the drm-msm 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, 6 Dec 2020 23:05:30 +0200
From:   Iskren Chernev <iskren.chernev@...il.com>
To:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Rob Clark <robdclark@...il.com>,
        Sean Paul <seanpaul@...omium.org>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        ~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: linux-next: Fixes tag needs some work in the drm-msm tree

On 12/6/20 10:05 PM, Stephen Rothwell wrote:
 > Hi all,
 >
 > In commit
 >
 >   9b73bde39cf2 ("drm/msm: Fix use-after-free in msm_gem with carveout")
 >
 > Fixes tag
 >
 >   Fixes: 4b85f7f5cf7 ("drm/msm: support for an arbitrary number of 
address spaces")
 >
 > has these problem(s):
 >
 >   - SHA1 should be at least 12 digits long
 >
 > In the furture, this can be avoided 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").

I'm sorry, I copied and truncated the hash by hand. I should have used

     git log --pretty=reference

Also scripts/checkpatch.pl didn't notice it. Should I submit v3 of the
patch or it's too late.

Regards,
Iskren