lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 05 Dec 2018 09:33:20 +0000
Subject: [Bug 201685] ext4 file system corruption

--- Comment #265 from Ortwin Gl├╝ck ( ---
I think Jens pretty much summarized the situation in #245. To trigger the bug
blk-mq must be used together with an underlying block device (such as SCSI or
SATA) that is stateful after a rejected bio submit. Then it's just a matter of
enough concurrent I/O.

So a workaround is to just disable blk-mq with SCIS: scsi_mod.use_blk_mq=1

You are receiving this mail because:
You are watching the assignee of the bug.

Powered by blists - more mailing lists