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: <E2E16098-2A6E-4300-A17A-FA7C2E140B23@redhat.com>
Date: Thu, 12 Sep 2024 11:06:59 -0400
From: Benjamin Coddington <bcodding@...hat.com>
To: Chuck Lever III <chuck.lever@...cle.com>,
 Christian Brauner <brauner@...nel.org>
Cc: 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 Kernel Mailing List <linux-kernel@...r.kernel.org>,
 gfs2@...ts.linux.dev, ocfs2-devel@...ts.linux.dev
Subject: Re: [PATCH v1 0/4] Fixup NLM and kNFSD file lock callbacks

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

No problem for me to send a v2 with these if needed.

Ben