Herbert,
> The crypto notify call occurs with a read mutex held so you must not > do any substantial work directly. In particular, you cannot call > crypto_alloc_* as they may trigger further notifications which may > dead-lock in the presence of another writer. > > This patch fixes this by postponing the work into a work queue and > taking the same lock in the module init function. No particular objections to this approach from me. Reviewed-by: Martin K. Petersen <martin.peter...@oracle.com> -- Martin K. Petersen Oracle Linux Engineering
