linux-kernel - Re: [PATCH v1 0/4] Fixup NLM and kNFSD file lock callbacks

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: <D0E3A915-E146-46C9-A64E-1B6CC2C631F4@oracle.com>
Date: Thu, 12 Sep 2024 18:17:06 +0000
From: Chuck Lever III <chuck.lever@...cle.com>
To: Benjamin Coddington <bcodding@...hat.com>
CC: Christian Brauner <brauner@...nel.org>, Jeff Layton <jlayton@...nel.org>,
        Amir Goldstein <amir73il@...il.com>, Neil Brown <neilb@...e.de>,
        Trond
 Myklebust <trondmy@...nel.org>,
        Anna Schumaker <anna@...nel.org>, Jonathan
 Corbet <corbet@....net>,
        Andreas Gruenbacher <agruenba@...hat.com>,
        Mark
 Fasheh <mark@...heh.com>, Joel Becker <jlbec@...lplan.org>,
        Joseph Qi
	<joseph.qi@...ux.alibaba.com>,
        Al Viro <viro@...iv.linux.org.uk>, Jan Kara
	<jack@...e.cz>,
        Alexander Ahring Oder Aring <aahringo@...hat.com>,
        Linux FS
 Devel <linux-fsdevel@...r.kernel.org>,
        Linux NFS Mailing List
	<linux-nfs@...r.kernel.org>,
        "linux-doc@...r.kernel.org"
	<linux-doc@...r.kernel.org>,
        Linux Kernel Mailing List
	<linux-kernel@...r.kernel.org>,
        "gfs2@...ts.linux.dev"
	<gfs2@...ts.linux.dev>,
        "ocfs2-devel@...ts.linux.dev"
	<ocfs2-devel@...ts.linux.dev>
Subject: Re: [PATCH v1 0/4] Fixup NLM and kNFSD file lock callbacks



> On Sep 12, 2024, at 11:06 AM, Benjamin Coddington <bcodding@...hat.com> wrote:
> 
> On 12 Sep 2024, at 10:01, Chuck Lever III wrote:
> 
>> For the NFSD and exportfs hunks:
>> 
>> Acked-by: Chuck Lever <chuck.lever@...cle.com <mailto:chuck.lever@...cle.com>>
>> 
>> "lockd: introduce safe async lock op" is in v6.10. Does this
>> series need to be backported to v6.10.y ? Should the series
>> have "Fixes: 2dd10de8e6bc ("lockd: introduce safe async lock
>> op")" ?
> 
> Thanks Chuck! Probably yes, if we want notifications fixed up there.  It
> should be sufficient to add this to the signoff area for at least the first
> three (and fourth for cleanup):
> 
> Cc: <stable@...r.kernel.org> # 6.10.x

2dd10de8e6bc landed in v6.7.

I suppose that since v6.10.y is likely to be closed by
the time this series is applied upstream, this tag might
be confusing.

Thus Fixes: 2dd10de8e6bc and a plain Cc: stable should
work best. Then whichever stable kernel is open when your
fixes are merged upstream will automatically get fixed.

None of the current LTS kernels have 2dd10de8e6bc so they
aren't relevant at this point.

--
Chuck Lever