linux-kernel - Re: linux-next: Fixes tag needs some work in the nfs 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]

Message-ID: <6af3f3273703c29dad890934a7fdb14153858ff8.camel@gmail.com>
Date: Mon, 14 Jul 2025 15:30:11 -0700
From: Trond Myklebust <trondmy@...il.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Christoph Hellwig <hch@....de>, 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 nfs tree

On Tue, 2025-07-15 at 07:57 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> In commit
> 
>   dad2fe3c563d ("NFS: drop __exit from nfs_exit_keyring")
> 
> Fixes tag
> 
>   Fixes: 2c285621176c ("nfs: create a kernel keyring")
> 
> has these problem(s):
> 
>   - Target SHA1 does not exist
> 
> Maybe you meant
> 
> Fixes: 6a247819238d ("nfs: create a kernel keyring")

Thanks! Fixed, and ditto with the other one.

-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trondmy@...nel.org, trond.myklebust@...merspace.com