kafs-client (recent strangeness of with add_key)

[Spencer Olson]

I added some very minor updates to my kafs-client repository on github:
https://github.com/olsonse/kafs-client

Mostly merges and fixes some debug/verbosity info that Bill had put
in.  My version still has the debian packing directly in the
repository and generates the changelog and copyright based on the git
history and existing other documentation.

I have been using this pretty successfully on my own isolated cell for
some time (using my own computer as the guinea pig).  In fact, I just
found that a milling machine I assembled cannot use OpenAFS and must
use kafs because of the realtime/preempt kernel that is required to be
used for the mill (the openafs kernel module refuses to build because
of some GPL problems).

In the last month or so, I've noticed that aklog-kafs has not been
working properly all the time.  The library call to "add_key" does not
always result in the afs tokens being stored in the session keyring.
I think this is pretty strange.  There are no errors that I can find
and nothing in the system log files that seem to indicate why the key
does not actually get stored.

I can't remember which kernel update this started for me with.  I am
currently running 5.13-0-44 (provided by Ubuntu).  I'm not entirely
sure this started with a kernel update either, but it seemed to start
very close in time when I had run a normal apt upgrade.  When this
first started, it seemed that I just couldn't get this to work at all.
Currently, it seems that a reboot fixes this.

Any thoughts, or even hints as to where to look for more debug info?
I do have auditd running and haven't found anything in those log files
that elluciates this situation.

Spencer