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>] [day] [month] [year] [list]
Date:   Thu, 12 Apr 2018 16:38:59 +0200
From:   Nikola Ciprich <>
Subject: delayed allocation vs WRITE SAME issue


i noticed following  warnings:

[52455.961319] sd 4:1:4:0: [sda] tag#11 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[52455.961322] sd 4:1:4:0: [sda] tag#11 Sense Key : Illegal Request [current]
[52455.961324] sd 4:1:4:0: [sda] tag#11 Add. Sense: No additional sense information
[52455.961327] sd 4:1:4:0: [sda] tag#11 CDB: Write Same(10) 41 00 01 1c 3b 28 00 00 08 00
[52455.961329] print_req_error: I/O error, dev sda, sector 18627368
[52455.961339] EXT4-fs (dm-3): Delayed block allocation failed for inode 393338 at logical offset 1125 with max blocks 1 with error 5
[52455.961342] EXT4-fs (dm-3): This should not happen!! Data will be lost

the culprit is FUSION-MPT SAS adapter, which apparently doesn't implement
WRITE SAME correctly. I've reported this to linux-scsi list (and fixed
it by blaklisting the feature  for the module for now).

but my concern is whether this case should not be handled somehow by ext4 delayed
allocation code as well? (well actually I wasn't able to verify any real fs corruption
so maybe it's just false warning, but still it's not very nice :))

I can easily reproduce the problem if it can help. tested on 4.14.16 kernel.

If I can provide any further info, please let me know.



Ing. Nikola CIPRICH, s.r.o.
28.rijna 168, 709 00 Ostrava

tel.:   +420 591 166 214
fax:    +420 596 621 273
mobil:  +420 777 093 799

mobil servis: +420 737 238 656
email servis:

Powered by blists - more mailing lists