FS#73611 - [cryfs] only single-threaded encryption key derivation
Attached to Project:
Community Packages
Opened by Nimrod Maclomhair (nimrod_mack) - Thursday, 03 February 2022, 13:39 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 05 February 2022, 18:54 GMT
Opened by Nimrod Maclomhair (nimrod_mack) - Thursday, 03 February 2022, 13:39 GMT
Last edited by Antonio Rojas (arojas) - Saturday, 05 February 2022, 18:54 GMT
|
Details
Description:
One or two versions ago, cryfs used to able to fully utilize multicore CPUs to derive the encryption key. At least in cryfs-0.11.1, this does not work anymore and only one core is used, thereby significantly slowing the mounting process. I would think this bug is not upstream, as I wasn't able to find a bug report on their github site. It seems to me that this has to do with OpenMP not being recognized correctly by cmake during the build, maybe? Additional info: * package version(s) the package cryfs-0.11.1 is affected * config and/or log files etc. * link to upstream bug report, if any Steps to reproduce: 1.) Try to mount cryfs filesystem 2.) observe CPU usage per core |
This task depends upon
Closed by Antonio Rojas (arojas)
Saturday, 05 February 2022, 18:54 GMT
Reason for closing: Fixed
Additional comments about closing: cryfs 0.11.1-2
Saturday, 05 February 2022, 18:54 GMT
Reason for closing: Fixed
Additional comments about closing: cryfs 0.11.1-2
Comment by Antonio Rojas (arojas) -
Thursday, 03 February 2022, 15:10 GMT
Comment by
Nimrod Maclomhair (nimrod_mack) -
Saturday, 05 February 2022, 10:23 GMT
Please report it upstream. -fopenmp is used during build, but the
resulting binary is actually not linked to libgomp.so. This is
likely caused by the update of the bundled crypto++.
Thanks for the insights! Reported upstream:
https://github.com/cryfs/cryfs/issues/414
- So this report can probably be closed.