On 08/09/2017 03:38 PM, h...@lst.de wrote:
Does commit 615d22a51c04856efe62af6e1d5b450aaf5cc2c0
"block: Fix __blkdev_issue_zeroout loop" fix the issue for you?
I crashed the 4.13-rc4 with the test above (blkdiscard -z on dm-crypt
dev). Unfortunately I hadn't have my VM configured properly so
On 06/19/2017 04:20 PM, Mike Snitzer wrote:
Looks like submit_flush_bio() is disabling/enabling interrupts from
interrupt context. Ondrej, does this patch fix the issue?
I let it spin for 30 minutes on patched dm-integrity and everything
seems ok now. The moment I loaded back the old one it
same log again, hopefully prettier format. Sorry:
[ 330.980914] DEBUG_LOCKS_WARN_ON(current->hardirq_context)
[ 330.980923] [ cut here ]
[ 330.982627] WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:2748
trace_hardirqs_on_caller+0x107/0x180
[ 330.984340] Modules
Hi,
cryptsetup testsuite easily triggers following crash. I can provide more
info on demand, but currently most straightforward way to trigger it is:
1) checkout cryptsetup master branch
(https://gitlab.com/cryptsetup/cryptsetup.git)
2)./autogen.sh --disable-python --enable-integritysetup
