dm integrity: fix to not disable/enable interrupts from interrupt context
authorMike Snitzer <snitzer@redhat.com>
Mon, 19 Jun 2017 14:55:47 +0000 (10:55 -0400)
committerMike Snitzer <snitzer@redhat.com>
Wed, 21 Jun 2017 15:45:02 +0000 (11:45 -0400)
commit7def52b78a5fda14864aab9b6fd14f09a4d4ff72
treefa4686fb458fd43860bca7b069bc5ff967d0e975
parentcd15fb64ee56192760ad5c1e2ad97a65e735b18b
dm integrity: fix to not disable/enable interrupts from interrupt context

Use spin_lock_irqsave and spin_unlock_irqrestore rather than
spin_{lock,unlock}_irq in submit_flush_bio().

Otherwise lockdep issues the following warning:
  DEBUG_LOCKS_WARN_ON(current->hardirq_context)
  WARNING: CPU: 1 PID: 0 at kernel/locking/lockdep.c:2748 trace_hardirqs_on_caller+0x107/0x180

Reported-by: Ondrej Kozina <okozina@redhat.com>
Tested-by: Ondrej Kozina <okozina@redhat.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
Acked-by: Mikulas Patocka <mpatocka@redhat.com>
drivers/md/dm-integrity.c