Linux NFS development
 help / color / mirror / Atom feed
From: Abdifatah Suruur <suruurism@gmail.com>
To: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] lockd: fix use-after-free in nlmsvc_retry_blocked()
Date: Thu, 15 Oct 2026 10:28:47 -0700 (PDT)	[thread overview]
Message-ID: <6ad10d4f.869db401.313f36.ee1e@mx.google.com> (raw)
In-Reply-To: <6dbeec76-a55d-4e41-9115-99d199997497@slotpi15m67>

Resending in plain text: the list rejected my earlier reply as HTML.
Chuck already has this; apologies for the duplicate.

Hi Chuck,

Thanks for the quick review and the detailed explanation -- both points
are well taken.

On the retry path: I hadn't checked nfsd-testing before sending; agreed,
it's the same fix in the same place. I'll drop this patch and base any
future lockd/NFSD work on your nfsd-testing branch.

On nlmsvc_notify_blocked(): you're right, and thanks for spelling it
out. I missed that __locks_wake_up_blocks() clears waiter->flc_blocker
only after lm_notify returns (the smp_store_release in fs/locks.c), so
any concurrent locks_delete_block() from the GRANT_RES/CANCEL paths has
to acquire blocked_lock_lock and wait for the callback to finish. The
list reference can't be dropped between the spin_unlock() and the
svc_wake_up(), so there's no window there. Please disregard that hunk.

Thanks again for the explanation -- it also tells me where to look next
time.

Regards,
Abdifatah

      reply	other threads:[~2026-10-15 17:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 20:22 [PATCH] lockd: fix use-after-free in nlmsvc_retry_blocked() Abdifatah Suruur
2026-10-01  1:07 ` Chuck Lever
2026-10-15 17:28   ` Abdifatah Suruur [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6ad10d4f.869db401.313f36.ee1e@mx.google.com \
    --to=suruurism@gmail.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox