Yes - it prevents construct_key_and_link() from going on to call
construct_key(). The key in question is returned in *_key.
However, I don't think I handle other errors coming back from
construct_alloc_key() correctly.
It should. In fact, I should probably precheck and preallocate the keyring to
make sure I don't get errors after allocating the new key.
No. We have to hold a write lock on the keyring semaphore if we're going to
call __key_link() to add something to it.
We should, however, call rcu_dereference_protected().
You should find a patch for this in your inbox.
David
--