This is a note to let you know that I've just added the patch titled
dm btree: silence lockdep lock inversion in dm_btree_del()
to the 4.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
dm-btree-silence-lockdep-lock-inversion-in-dm_btree_del.patch
and it can be found in the queue-4.1 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@xxxxxxxxxxxxxxx> know about it.
>From 1c7518794a3647eb345d59ee52844e8a40405198 Mon Sep 17 00:00:00 2001
From: Joe Thornber <ejt@xxxxxxxxxx>
Date: Fri, 3 Jul 2015 14:51:32 +0100
Subject: dm btree: silence lockdep lock inversion in dm_btree_del()
From: Joe Thornber <ejt@xxxxxxxxxx>
commit 1c7518794a3647eb345d59ee52844e8a40405198 upstream.
Allocate memory using GFP_NOIO when deleting a btree. dm_btree_del()
can be called via an ioctl and we don't want to recurse into the FS or
block layer.
Signed-off-by: Joe Thornber <ejt@xxxxxxxxxx>
Signed-off-by: Mike Snitzer <snitzer@xxxxxxxxxx>
Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
---
drivers/md/persistent-data/dm-btree.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/md/persistent-data/dm-btree.c
+++ b/drivers/md/persistent-data/dm-btree.c
@@ -255,7 +255,7 @@ int dm_btree_del(struct dm_btree_info *i
int r;
struct del_stack *s;
- s = kmalloc(sizeof(*s), GFP_KERNEL);
+ s = kmalloc(sizeof(*s), GFP_NOIO);
if (!s)
return -ENOMEM;
s->info = info;
Patches currently in stable-queue which might be from ejt@xxxxxxxxxx are
queue-4.1/dm-btree-remove-fix-bug-in-redistribute3.patch
queue-4.1/dm-btree-silence-lockdep-lock-inversion-in-dm_btree_del.patch
queue-4.1/dm-cache-fix-race-when-issuing-a-policy_replace-operation.patch
queue-4.1/dm-thin-allocate-the-cell_sort_array-dynamically.patch
queue-4.1/dm-space-map-metadata-fix-occasional-leak-of-a-metadata-block-on-resize.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html