Documentation: no parallel socket operations on AF_KTLS and bound socket are possible without explicit synchronization

Question

Documentation: no parallel socket operations on AF_KTLS and bound socket are possible without explicit synchronization

Closed this issue 8 years ago · 3 comments

Bound UDP/TCP sockets should be locked while we are doing operations in AF_KTLS since (not only) userspace can operate on them in parallel with AF_KTLS and that could lead to inconstancy; pseudocode:

in AF_KTLS:                                   userspace:
read(sd, ktls_buf, size, MSG_PEEK)

decrypt                                         !!! read(sd, buf2, size, 0)

!!! pop_record(sd)

Answer 1 · 2016-04-25T13:07:58.000Z

related: https://github.com/fridex/af_ktls/issues/21

Answer 2 · 2016-04-25T14:27:07.000Z

Since socket locking is done inside socket operations (bound socket), we cannot lock it in AF_KTLS. Synchronization has to be done explicitly in user space if necessary. So this should be considered as "not a bug", but this should be explicitly stated in documentation (no parallel socket operations on AF_KTLS and bound socket are possible without explicit synchronization).

Answer 3 · 2016-08-17T19:09:55.000Z

Not a bug. Closing