FAILED: patch "[PATCH] RDMA/odp: Fix missed unlock in non-blocking invalidate_start" failed to apply to 4.19-stable tree
Subsystems (2)
[email protected]
maintainerThe patch below does not apply to the 4.19-stable tree.
If someone wants it applied there, or to any other stable or longterm tree, then please email the backport, including the original git commit id to <[email protected]>.
thanks,
greg k-h
------------------ original commit in Linus's tree ------------------
From 7608bf40cf2480057ec0da31456cc428791c32ef Mon Sep 17 00:00:00 2001
From: Jason Gunthorpe <[email protected]>
Date: Tue, 11 Jun 2019 13:09:51 -0300
Subject: [PATCH] RDMA/odp: Fix missed unlock in non-blocking invalidate_start
If invalidate_start returns with EAGAIN then the umem_rwsem needs to be unlocked as no invalidate_end will be called.
Cc <[email protected]>
Fixes ca748c39ea3f ("RDMA/umem: Get rid of per_mm->notifier_count")
Signed-off-by Jason Gunthorpe <[email protected]>
Reviewed-by Leon Romanovsky <[email protected]>
Signed-off-by Doug Ledford <[email protected]>
drivers/infiniband/core/umem_odp.c +9 -5
@@ -149,6 +149,7 @@ static int ib_umem_notifier_invalidate_range_start(struct mmu_notifier *mn, {struct ib_ucontext_per_mm *per_mm = container_of(mn, struct ib_ucontext_per_mm, mn); +int rc;if (mmu_notifier_range_blockable (range))down_read (&per_mm->umem_rwsem);
@@ -165,11 +166,14 @@ static int ib_umem_notifier_invalidate_range_start(struct mmu_notifier *mn,return 0 ; } -return rbt_ib_umem_for_each_in_range (&per_mm->umem_tree, range->start, - range->end, - invalidate_range_start_trampoline, -mmu_notifier_range_blockable (range), -NULL ); + rc =rbt_ib_umem_for_each_in_range (&per_mm->umem_tree, range->start, + range->end, + invalidate_range_start_trampoline, +mmu_notifier_range_blockable (range), +NULL ); +if (rc) +up_read (&per_mm->umem_rwsem); +return rc; } static int invalidate_range_end_trampoline(struct ib_umem_odp *item, u64 start,