summaryrefslogtreecommitdiffstats
path: root/crypto/md4.c
diff options
context:
space:
mode:
authorJason Gunthorpe <jgg@mellanox.com>2018-09-16 20:48:10 +0300
committerDoug Ledford <dledford@redhat.com>2018-09-21 11:58:36 -0400
commitbe7a57b41ad824dbc59d1ffa91160ee73f2999ee (patch)
tree4169879247114dbfd027d0da322fc6f1dbf4c82e /crypto/md4.c
parentca748c39ea3f3c755295d64d69ba0b4375e34b5d (diff)
downloadlinux-be7a57b41ad824dbc59d1ffa91160ee73f2999ee.tar.bz2
RDMA/umem: Handle a half-complete start/end sequence
mmu_notifier_unregister() can race between a invalidate_start/end and cause the invalidate_end to be skipped. This causes an imbalance in the locking, which lockdep complains about. This is not actually a bug, as we immediately kfree the memory holding the lock, but it simple enough to fix. Mark when the notifier is being destroyed and abort the start callback. This can be done under the lock we already obtained, and can re-purpose the invalidate_range test we already have. Signed-off-by: Jason Gunthorpe <jgg@mellanox.com> Signed-off-by: Leon Romanovsky <leonro@mellanox.com> Signed-off-by: Doug Ledford <dledford@redhat.com>
Diffstat (limited to 'crypto/md4.c')
0 files changed, 0 insertions, 0 deletions