diff options
| author | Chao Yu | 2019-03-05 10:52:33 +0100 |
|---|---|---|
| committer | Jaegeuk Kim | 2019-03-13 02:59:19 +0100 |
| commit | 2a6a7e722e7a78d774ce02b847c5b183a3ff2672 (patch) | |
| tree | 19999aec25b4f3b965046b4dfb863a3a9b61f8f9 /.gitignore | |
| parent | f2fs: print more parameters in trace_f2fs_map_blocks (diff) | |
| download | kernel-qcow2-linux-2a6a7e722e7a78d774ce02b847c5b183a3ff2672.tar.gz kernel-qcow2-linux-2a6a7e722e7a78d774ce02b847c5b183a3ff2672.tar.xz kernel-qcow2-linux-2a6a7e722e7a78d774ce02b847c5b183a3ff2672.zip | |
f2fs: fix to use kvfree instead of kzfree
As Jiqun Li reported in bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=202747
System can panic due to using wrong allocate/free function pair
in xattr interface:
- use kvmalloc to allocate memory
- use kzfree to free memory
Let's fix to use kvfree instead of kzfree, BTW, we are safe to
get rid of kzfree, since there is no such confidential data stored
as xattr, we don't need to zero it before free memory.
Fixes: 5222595d093e ("f2fs: use kvmalloc, if kmalloc is failed")
Reported-by: Jiqun Li <jiqun.li@unisoc.com>
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to '.gitignore')
0 files changed, 0 insertions, 0 deletions