Control: reassign -1 libnvme1 Control: found -1 1.5-1 Control: affects -1 udisks2 Control: retitle -1 stack smashing detected in libnvme
Hi Marc Am 23.07.23 um 12:07 schrieb Marc Bres Gil:
Hello Michael,I went to upstream with the traces, and found an already reported bug there on issues after updating to 2.10 with kde plasma (https://github.com/storaged-project/udisks/issues/1139 <https://github.com/storaged-project/udisks/issues/1139>) . Added the info to that bug report, for what I understand from the gdb trace, seems related to some nvme function. Will see if it helps there.
Quoting from the upstream bug report
nvme sanitize-log -H /dev/nvme0:
Progress (SPROG) : 65535
Sanitize Status (SSTAT) : 0x1
[2:0] Most Recent Sanitize Command Completed Successfully.
[7:3] Number of completed passes if most recent operation was
overwrite: 0
[8] Global Data Erased cleared: a NS LB in the NVM subsystem has
been written to or a PMR in the NVM subsystem has been enabled
Sanitize Command Dword 10 Information (SCDW10) : 0
Estimated Time For Overwrite : 0
Estimated Time For Block Erase : 0
Estimated Time For Crypto Erase : 0
Estimated Time For Overwrite (No-Deallocate) : 0
Estimated Time For Block Erase (No-Deallocate) : 0
Estimated Time For Crypto Erase (No-Deallocate): 0
*** stack smashing detected ***: terminated
Avortat
I.e., this issue is coming from libnvme1, thus reassigning accordingly and marking udisks2 as affected.
@Daniel: The upstream bug report [1] has some more info, like backtraces etc. Maybe you have an idea what's causing this issue.
Regards, Michael
OpenPGP_signature
Description: OpenPGP digital signature
