On Mon, May 23, 2022 at 03:36:27PM -0400, Jeff Layton wrote: > The other lockowner _is_ involved. It's the one holding the conflicting > lock. nfs4_set_lock_denied copies info from the conflicting lockowner > into the LOCK/LOCKT response. That's safe now because it holds a > reference to the owner. At one point it wasn't (see commit aef9583b234a4 > "NFSD: Get reference of lockowner when coping file_lock", which fixed > that). I doubt that commit fixed the whole problem, for what it's worth. What if the client holding the conflicting lock expires before we get to nfs4_set_lock_denied? --b.
