On Tue, Nov 05, 2019 at 01:11:22PM +0200, Jarkko Sakkinen wrote: > I'll add @count to address this. This output field will contain the > number of bytes actually written instead of overwriting input > parameters, which is a bad practice in anyway. > > We don't need to actually cap to anything but API must be able to > support such scenario. Caller must be prepared to deal with the > situation where the return value is zero but @count < @length. I summarized here my reasoning on @count: https://lore.kernel.org/linux-sgx/20191108081331.GB3370@xxxxxxxxxxxxxxx/ /Jarkko
