always set op

[dmah42]

during investigation of #1 I noticed userspace always logs a set op as opposed to add, etc. as set is index 0 this is suspicious.

op is part of entry as is key, and key is sent through correctly.

maybe a padding/nested struct thing? check generated code I guess...

[dmah42]

checked output and byte-by-byte it was identical between kernel and user space. however, there seemed to be an extra 4 bytes of 0 between the key (inner) and rest of the outer entry struct in both that shouldn't be there, leading to op being read as 0 (SET).

unnested the struct used over the wire and everything works.