https://bugzilla.kernel.org/show_bug.cgi?id=201685

Azat Khuzhin (a3at.mail@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |a3at.mail@gmail.com

--- Comment #31 from Azat Khuzhin (a3at.mail@gmail.com) ---

I'm also running 4.20-rc2 but does not experience any corruption for now
(*crossing fingers*)

(In reply to Theodore Tso from comment #11)

hmm, my laptop running 4.19.0 plus the ext4 commits landing in 4.20-rc2+ is
*also* using CONFIG_SCSI_MQ_DEFAULT=n

But I do have CONFIG_SCSI_MQ_DEFAULT:

$ zgrep CONFIG_SCSI_MQ_DEFAULT=y /proc/config.gz
CONFIG_SCSI_MQ_DEFAULT=y
$ head /sys/block/dm-0/dm/use_blk_mq
1

(In reply to Jens Axboe from comment #25)

Ted, it seems to be affecting nvme as well

And I do have nvme ssd:

nvme0n1       259:0    0 953.9G  0 disk
├─nvme0n1p1   259:1    0   260M  0 part  /boot
└─nvme0n1p2   259:2    0 953.6G  0 part
  └─cryptroot 254:0    0 953.6G  0 crypt /

And as you can see I have dm-crypt

So it looks like that this is not that simple (IOW not every setup/env/hw
affected).

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