nfsd4_has_a...async_copies(9)

💖 nfsd4_has_a...async_copies(9) 💖

okay bestie, welcome to the Kernel API Manual page for this little NFSD helper. It's giving kernel-internals realness, but we're gonna make it make sense 💅

🌸 NAME 🌸

nfsd4_has_active_async_copies — check for ongoing copy operations 👑

🦋 SYNOPSIS 🦋

bool nfsd4_has_active_async_copies (struct nfs4_client *clp );

🎀 ARGUMENTS 🎀

• clp — the client to be checked. That's the whole vibe check target 🫶

✨ DESCRIPTION ✨

So NFSD keeps state for async COPY operations after they complete, and that state stays in the nfs4_client's async_copies list. Iconic, but also: care needed.

Ongoing copies should block the destruction of the nfs4_client, but completed copies should not. No cap. That's the whole point of checking.

💫 Return values 💫

• true — At least one active async COPY is ongoing 🔥
• false — No active async COPY operations were found 💀

🌈 SEE ALSO 🌈

• Kernel file ./fs/nfsd/nfs4proc.c set_change_info(9)
• nfsd4_async_copy_reaper(9)
• nfsd4_cancel_copy_by_sb(9)
• nfsd4_do_async_copy(9)
• nfsd4_spo_must_allow(9)

so yeah, that's the page 💖 it comes from ./fs/nfsd, dated October 2026, and it's the nfsd4_has_a...async_copies(9) page — bye bestie, go check those copies 🌸