Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #91373

Bug#1128861: Acknowledgement (linux: when serving NFS, client attempts to lock served files fail with "No locks available")

From Philip Hands <phil@hands.com>
Newsgroups linux.debian.bugs.dist, linux.debian.kernel
Subject Bug#1128861: Acknowledgement (linux: when serving NFS, client attempts to lock served files fail with "No locks available")
Date 2026-02-24 01:30 +0100
Message-ID <MrOtj-2QY5-1@gated-at.bofh.it> (permalink)
References <MrJWG-2NTx-3@gated-at.bofh.it> <MrMBb-2PIv-3@gated-at.bofh.it> <MrNGV-2Qpy-1@gated-at.bofh.it> <MrJWG-2NTx-3@gated-at.bofh.it> <MrNGV-2Qpy-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw


Philip Hands <phil@hands.com> writes:

> Here's a bisect log:
>
...
> # good: [18744bc56b0ec34b0fe397ee71c2ffdc48c6a0e0] nfsd: refine and rename NFSD_MAY_LOCK
> git bisect good 18744bc56b0ec34b0fe397ee71c2ffdc48c6a0e0

It seems that ^ was a mistake on my part -- having retested
18744bc56b0ec34 it is in fact bad.

Back to linux.debian.kernel | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

Bug#1128861: linux: when serving NFS, client attempts to lock served files fail with "No locks available" Philip Hands <phil@hands.com> - 2026-02-23 20:40 +0100
  Bug#1128861: Acknowledgement (linux: when serving NFS, client attempts to lock served files fail with "No locks available") Philip Hands <phil@hands.com> - 2026-02-23 23:30 +0100
  Bug#1128861: Acknowledgement (linux: when serving NFS, client attempts to lock served files fail with "No locks available") Philip Hands <phil@hands.com> - 2026-02-24 00:40 +0100
    Bug#1128861: Acknowledgement (linux: when serving NFS, client attempts to lock served files fail with "No locks available") Philip Hands <phil@hands.com> - 2026-02-24 01:30 +0100
  Bug#1128861: Revert 18744bc56b0ec appears to resolve it Tj <tj.iam.tj@proton.me> - 2026-02-24 01:50 +0100
  Bug#1128861: Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available Tj <tj.iam.tj@proton.me> - 2026-02-24 03:20 +0100
    Bug#1128861: Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available Tj <tj.iam.tj@proton.me> - 2026-02-24 14:00 +0100
    Bug#1128861: Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available Thorsten Leemhuis <regressions@leemhuis.info> - 2026-02-27 11:10 +0100
      Bug#1128861: Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available Salvatore Bonaccorso <carnil@debian.org> - 2026-03-04 11:40 +0100
    Bug#1128861: Regression: Missing check in nfsd_permission() causes -ENOLCK No locks available Sasha Levin <sashal@kernel.org> - 2026-03-04 16:50 +0100
  Processed: Re: Bug#1128861: Regression: Missing check in  nfsd_permission() causes -ENOLCK No locks available "Debian Bug Tracking System" <owner@bugs.debian.org> - 2026-03-04 11:40 +0100
  Bug#1128861: [PATCH] lockd: fix TEST handling when not all permissions are available. Ben Hutchings <ben@decadent.org.uk> - 2026-03-25 21:40 +0100

csiph-web