linux-kernel - Re: [git pull] habanalabs pull request for kernel 5.9-rc1 (resend)

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]

Message-ID: <20200724093259.GB4116407@kroah.com>
Date:   Fri, 24 Jul 2020 11:32:59 +0200
From:   Greg KH <gregkh@...uxfoundation.org>
To:     Oded Gabbay <oded.gabbay@...il.com>
Cc:     linux-kernel@...r.kernel.org
Subject: Re: [git pull] habanalabs pull request for kernel 5.9-rc1 (resend)

On Thu, Jul 23, 2020 at 10:15:25PM +0300, Oded Gabbay wrote:
> Hello Greg,
> 
> (Re-sending this pull request)
> 
> This is habanalabs pull request for the merge window of kernel 5.9. It
> contains many small improvements to common and GAUDI code. Details are in
> the tag.
> 
> Thanks,
> Oded
> 
> The following changes since commit 7a4462a96777b64b22412f782de226c90290bf75:
> 
>   misc: rtsx: Use standard PCI definitions (2020-07-22 13:39:31 +0200)
> 
> are available in the Git repository at:
> 
>   git://people.freedesktop.org/~gabbayo/linux tags/misc-habanalabs-next-2020-07-23

{sigh}

Commit: 961a7325e670 ("habanalabs: Fix memory leak in error flow of context init")
	Fixes tag: Fixes: 786c94810698 ("habanalabs: Use pending cs amount per asic")
	Has these problem(s):
	        - Subject does not match target commit subject
	          Just use
		                git log -1 --format='Fixes: %h ("%s")'

The scripts I use to check this are here:
	https://github.com/gregkh/gregkh-linux/blob/master/work/verify_fixes.sh
	https://github.com/gregkh/gregkh-linux/blob/master/work/verify_signedoff.sh

And note, if I ignore these errors, you will just get the same response
from Stephen when it hits linux-next :(

thanks,

greg k-h