On Wed, May 29, 2024 at 06:50:34PM +0200, Kevin Wolf wrote: > Am 27.05.2024 um 17:58 hat Stefan Hajnoczi geschrieben: > > The block layer does not know how many threads will perform I/O. It is > > possible > > to exceed the number of threads that is given to qcrypto_block_open() and > > this > > can trigger an assertion failure in qcrypto_block_pop_cipher(). > > > > This patch series removes the n_threads argument and instead handles an > > arbitrary number of threads. > > --- > > Is it secure to store the key in QCryptoBlock? In this series I assumed the > > answer is yes since the QCryptoBlock's cipher state is equally sensitive, > > but > > I'm not familiar with this code or a crypto expert. > > I would assume the same, but I'm not merging this yet because I think > you said you'd like to have input from danpb? > > Reviewed-by: Kevin Wolf <kw...@redhat.com>
Yes, please wait until Dan comments. Thanks, Stefan
signature.asc
Description: PGP signature
