Re: [PATCH -next] hugetlbfs: a terminator for hugetlb_param_specs[]

2019-02-08 Thread Al Viro
On Fri, Feb 08, 2019 at 04:31:39PM +, David Howells wrote: > Mike Kravetz wrote: > > > Thanks for fixing this. Looks like a simple oversight when 2284cf59cbce > > was added. > > I've already pushed a fix for this which Al should have folded in already. It has been in -next since Tuesday.

Re: [PATCH -next] hugetlbfs: a terminator for hugetlb_param_specs[]

2019-02-08 Thread David Howells
Mike Kravetz wrote: > Thanks for fixing this. Looks like a simple oversight when 2284cf59cbce > was added. I've already pushed a fix for this which Al should have folded in already. > FYI David, the fs_parameter_spec example in the documentation (mount_api.txt) > is also missing a terminator.

Re: [PATCH -next] hugetlbfs: a terminator for hugetlb_param_specs[]

2019-02-04 Thread Mike Kravetz
On 2/4/19 5:22 PM, Qian Cai wrote: > Booting up an arm64 server with CONFIG_VALIDATE_FS_PARSER=n triggers a > out-of-bounds error below, due to the commit 2284cf59cbce ("hugetlbfs: > Convert to fs_context") missed a terminator for hugetlb_param_specs[], > and causes this loop in fs_lookup_key(), >

[PATCH -next] hugetlbfs: a terminator for hugetlb_param_specs[]

2019-02-04 Thread Qian Cai
Booting up an arm64 server with CONFIG_VALIDATE_FS_PARSER=n triggers a out-of-bounds error below, due to the commit 2284cf59cbce ("hugetlbfs: Convert to fs_context") missed a terminator for hugetlb_param_specs[], and causes this loop in fs_lookup_key(), for (p = desc->specs; p->name; p++) could n