Page MenuHomeFreeBSD

gssd: use netlink(4) RPC service to talk to kernel GSS
ClosedPublic

Authored by glebius on Jan 20 2025, 9:03 PM.
Tags
None
Referenced Files
F115983052: D48553.id150345.diff
Thu, May 1, 5:01 AM
F115929406: D48553.diff
Wed, Apr 30, 1:15 PM
Unknown Object (File)
Sat, Apr 12, 6:03 AM
Unknown Object (File)
Sun, Apr 6, 1:36 PM
Unknown Object (File)
Feb 14 2025, 12:40 AM
Unknown Object (File)
Feb 5 2025, 4:31 PM
Unknown Object (File)
Feb 3 2025, 2:57 AM
Unknown Object (File)
Feb 2 2025, 11:49 PM
Subscribers

Details

Summary

Userland counterpart of the previous commit.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Skipped
Unit
Tests Skipped
Build Status
Buildable 61826
Build 58710: arc lint + arc unit

Event Timeline

I think this looks fine. I cannot exactly remember what
the gssd_syscall("") did (it indicated the daemon was going away),
but I'll assume you no longer need it?

Does the kernel code know that the daemon has gone away so
that it will no longer attempt an upcall?

This revision is now accepted and ready to land.Jan 25 2025, 9:01 PM

Does the kernel code know that the daemon has gone away so
that it will no longer attempt an upcall?

Kernel will timeout the call. There is no way to quickly tell if there are any netlink listeners on the userland side. If we want to make a faster reaction of kernel to daemon failure we can play with timeouts algorithm. E.g. after first failure switch to very short timeout, so that we return in 1 second, but still leaving a chance for daemon to come up and then we will switch to a normal mode.