diff options
| author |   Liu Yuntao <liuyuntao10@huawei.com> | 2022-02-25 19:11:02 -0800 |
|---|---|---|
| committer |   Linus Torvalds <torvalds@linux-foundation.org> | 2022-02-26 09:51:17 -0800 |
| commit | e79ce9832316e09529b212a21278d68240ccbf1f (patch) | |
| tree | 6636ff389bbec8db1d3655f029febabe8893ee9a /tools/testing/selftests/bpf/prog_tests/autoload.c | |
| parent | kasan: test: prevent cache merging in kmem_cache_double_destroy (diff) | |
| download | wireguard-linux-e79ce9832316e09529b212a21278d68240ccbf1f.tar.xz wireguard-linux-e79ce9832316e09529b212a21278d68240ccbf1f.zip | |
hugetlbfs: fix a truncation issue in hugepages parameter
When we specify a large number for node in hugepages parameter, it may
be parsed to another number due to truncation in this statement:
node = tmp;
For example, add following parameter in command line:
hugepagesz=1G hugepages=4294967297:5
and kernel will allocate 5 hugepages for node 1 instead of ignoring it.
I move the validation check earlier to fix this issue, and slightly
simplifies the condition here.
Link: https://lkml.kernel.org/r/20220209134018.8242-1-liuyuntao10@huawei.com
Fixes: b5389086ad7be0 ("hugetlbfs: extend the definition of hugepages parameter to support node allocation")
Signed-off-by: Liu Yuntao <liuyuntao10@huawei.com>
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
Cc: <stable@vger.kernel.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'tools/testing/selftests/bpf/prog_tests/autoload.c')
0 files changed, 0 insertions, 0 deletions