diff options
| author | Mike Kravetz <mike.kravetz@oracle.com> | 2019-12-01 02:56:34 +0100 |
|---|---|---|
| committer | Linus Torvalds <torvalds@linux-foundation.org> | 2019-12-01 21:59:08 +0100 |
| commit | 8fc312b32b25c6b0a8b46fab4df8c68df5af1223 (patch) | |
| tree | 8d263f997d3cf396de30dadd86a3bb4526e82713 /.cocciconfig | |
| parent | hugetlbfs: hugetlb_fault_mutex_hash() cleanup (diff) | |
| download | linux-8fc312b32b25c6b0a8b46fab4df8c68df5af1223.tar.xz linux-8fc312b32b25c6b0a8b46fab4df8c68df5af1223.zip | |
mm/hugetlbfs: fix error handling when setting up mounts
It is assumed that the hugetlbfs_vfsmount[] array will contain either a
valid vfsmount pointer or NULL for each hstate after initialization.
Changes made while converting to use fs_context broke this assumption.
While fixing the hugetlbfs_vfsmount issue, it was discovered that
init_hugetlbfs_fs never did correctly clean up when encountering a vfs
mount error.
It was found during code inspection. A small memory allocation failure
would be the most likely cause of taking a error path with the bug.
This is unlikely to happen as this is early init code.
Link: http://lkml.kernel.org/r/94b6244d-2c24-e269-b12c-e3ba694b242d@oracle.com
Reported-by: Chengguang Xu <cgxu519@mykernel.net>
Fixes: 32021982a324 ("hugetlbfs: Convert to fs_context")
Signed-off-by: Mike Kravetz <mike.kravetz@oracle.com>
Cc: David Howells <dhowells@redhat.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to '.cocciconfig')
0 files changed, 0 insertions, 0 deletions