You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For KTLS only there is no need for async crypto API, since all encryption and decryption is called from userspace (the only time cryptd is used is if in bh context).
Unfortunately it looks like KCM + KTLS may call decrypt in bh context sometimes, so at least decrypt it may be necessary to set the proper async crypto callback.
The text was updated successfully, but these errors were encountered:
For KTLS only there is no need for async crypto API, since all encryption and decryption is called from userspace (the only time cryptd is used is if in bh context).
Unfortunately it looks like KCM + KTLS may call decrypt in bh context sometimes, so at least decrypt it may be necessary to set the proper async crypto callback.
The text was updated successfully, but these errors were encountered: