From: Michal Hocko <mhocko@suse.com>
Date: Thu, 28 Apr 2016 13:24:03 +0000 (+0200)
Subject: dm ioctl: drop use of __GFP_REPEAT in copy_params()'s __vmalloc() call
X-Git-Url: https://git.stricted.de/?a=commitdiff_plain;h=72f6d8d8c9b3592da7109cad3415559864ee9f2d;p=GitHub%2Fmoto-9609%2Fandroid_kernel_motorola_exynos9610.git

dm ioctl: drop use of __GFP_REPEAT in copy_params()'s __vmalloc() call

copy_params()'s use of __GFP_REPEAT for the __vmalloc() call doesn't make much
sense because vmalloc doesn't rely on costly high order allocations.

Signed-off-by: Michal Hocko <mhocko@suse.com>
Signed-off-by: Mike Snitzer <snitzer@redhat.com>
---

diff --git a/drivers/md/dm-ioctl.c b/drivers/md/dm-ioctl.c
index 2adf81d81fca..2c7ca258c4e4 100644
--- a/drivers/md/dm-ioctl.c
+++ b/drivers/md/dm-ioctl.c
@@ -1723,7 +1723,7 @@ static int copy_params(struct dm_ioctl __user *user, struct dm_ioctl *param_kern
 	if (!dmi) {
 		unsigned noio_flag;
 		noio_flag = memalloc_noio_save();
-		dmi = __vmalloc(param_kernel->data_size, GFP_NOIO | __GFP_REPEAT | __GFP_HIGH | __GFP_HIGHMEM, PAGE_KERNEL);
+		dmi = __vmalloc(param_kernel->data_size, GFP_NOIO | __GFP_HIGH | __GFP_HIGHMEM, PAGE_KERNEL);
 		memalloc_noio_restore(noio_flag);
 		if (dmi)
 			*param_flags |= DM_PARAMS_VMALLOC;