summaryrefslogtreecommitdiffstats
path: root/fs/ubifs/lprops.c
diff options
context:
space:
mode:
authorArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-03-24 16:14:26 +0200
committerArtem Bityutskiy <Artem.Bityutskiy@nokia.com>2011-03-24 16:14:26 +0200
commitfc5e58c0c4fd86881ec8ba8e46e41a07e25dc7a6 (patch)
tree21c1223c94bc366e48a7f4f5a19011f7defc7631 /fs/ubifs/lprops.c
parent3d46b316bcc1ecb17f8e7874a8ec620c64864898 (diff)
downloadop-kernel-dev-fc5e58c0c4fd86881ec8ba8e46e41a07e25dc7a6.zip
op-kernel-dev-fc5e58c0c4fd86881ec8ba8e46e41a07e25dc7a6.tar.gz
UBIFS: use GFP_NOFS properly
This patch fixes a brown-paperbag bug which was introduced by me: I used incorrect "GFP_KERNEL | GFP_NOFS" allocation flags to make sure my allocations do not cause write-back. But the correct form is "GFP_NOFS". Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
Diffstat (limited to 'fs/ubifs/lprops.c')
-rw-r--r--fs/ubifs/lprops.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/ubifs/lprops.c b/fs/ubifs/lprops.c
index c7b25e2..0ee0847 100644
--- a/fs/ubifs/lprops.c
+++ b/fs/ubifs/lprops.c
@@ -1094,7 +1094,7 @@ static int scan_check_cb(struct ubifs_info *c,
}
}
- buf = __vmalloc(c->leb_size, GFP_KERNEL | GFP_NOFS, PAGE_KERNEL);
+ buf = __vmalloc(c->leb_size, GFP_NOFS, PAGE_KERNEL);
if (!buf) {
ubifs_err("cannot allocate memory to scan LEB %d", lnum);
goto out;
OpenPOWER on IntegriCloud