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]
Message-ID: <YOPzwg7DeU1gobIr@kernel.org>
Date:   Tue, 6 Jul 2021 09:10:10 +0300
From:   Mike Rapoport <rppt@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Guenter Roeck <linux@...ck-us.net>,
        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 memblock-fixes tree

Hi Stephen,

On Tue, Jul 06, 2021 at 08:06:21AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   24caecffab46 ("arm: ioremap: don't abuse pfn_valid() to check if pfn is in RAM")
> 
> Fixes tag
> 
>   Fixes: 30603c5a0c9a ("arm: ioremap: don't abuse pfn_valid() to check if pfn
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> I could not easily find the actual commit that was meant.
> 
> Also, please do not split Fixes tags over more than one line.

Should be fixed now.

-- 
Sincerely yours,
Mike.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ