linux-kernel - Re: linux-next: duplicate patch in the nfsd 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: <B165D861-0AAF-430E-9083-6E4EE91D8E8A@oracle.com>
Date: Sun, 7 Jan 2024 23:04:21 +0000
From: Chuck Lever III <chuck.lever@...cle.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next
 Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the nfsd tree

> On Jan 7, 2024, at 4:19 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> Hi all,
> 
> The following commit is also in Linus Torvalds' tree as a different commit
> (but the same patch):
> 
>  76d296a82657 ("nfsd: drop the nfsd_put helper")
> 
> This is commit
> 
>  64e6304169f1 ("nfsd: drop the nfsd_put helper")
> 
> in Linus' tree.

Apparently my tool chain "touched" that commit after I pushed
it to nfsd-fixes but before I created the nfsd-6.7-3 tag. The
only difference I see between those two commits is the committer
date, and in my public git repo, git claims 76d296a82657 is not
on any branch.

I've reset the public nfsd-fixes branch to point to v6.7.

--
Chuck Lever