On (25/02/22 21:31), Sergey Senozhatsky wrote: > > As long as crypto drivers consistently return -ENOSP or a specific error > > code for dst_buf overflow, we should be able to eliminate the > > 2*PAGE_SIZE buffer. > > > > My point is: > > 1. All drivers must be capable of handling dst_buf overflow. > > 2. All drivers must return a consistent and dedicated error code for > > dst_buf overflow. So I didn't look at all of them, but at least S/W lzo1 doesn't even have a notion of max-output-len. lzo1x_1_compress() accepts a pointer to out_len which tells the size of output stream (the algorithm is free to produce any), so there is no dst_buf overflow as far as lzo1 is concerned. Unless I'm missing something or misunderstanding your points.
