From: Dan Carpenter <error27@gmail.com>
Date: Fri, 7 May 2010 09:05:33 +0000 (+0200)
Subject: exofs: confusion between kmap() and kmap_atomic() api
X-Git-Tag: firefly_0821_release~9833^2~2029^2
X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=ddf08f4b90a413892bbb9bb2e8a57aed991cd47d;p=firefly-linux-kernel-4.4.55.git

exofs: confusion between kmap() and kmap_atomic() api

For kmap_atomic() we call kunmap_atomic() on the returned pointer.
That's different from kmap() and kunmap() and so it's easy to get them
backwards.

Cc: Stable <stable@kernel.org>
Signed-off-by: Dan Carpenter <error27@gmail.com>
Signed-off-by: Boaz Harrosh <bharrosh@panasas.com>
---

diff --git a/fs/exofs/dir.c b/fs/exofs/dir.c
index 4cfab1cc75c0..d91e9d829bc1 100644
--- a/fs/exofs/dir.c
+++ b/fs/exofs/dir.c
@@ -608,7 +608,7 @@ int exofs_make_empty(struct inode *inode, struct inode *parent)
 	de->inode_no = cpu_to_le64(parent->i_ino);
 	memcpy(de->name, PARENT_DIR, sizeof(PARENT_DIR));
 	exofs_set_de_type(de, inode);
-	kunmap_atomic(page, KM_USER0);
+	kunmap_atomic(kaddr, KM_USER0);
 	err = exofs_commit_chunk(page, 0, chunk_size);
 fail:
 	page_cache_release(page);