On Fri, Jun 23, 2017 at 2:21 PM, Andrey Konovalov <andreyk...@google.com> wrote: > On Fri, Jun 23, 2017 at 12:29 AM, Cong Wang <xiyou.wangc...@gmail.com> wrote: >> The memory allocation size is controlled by user-space, >> if it is too large just fail silently and return NULL, >> not to mention there is a fallback allocation later. > > Thanks! > > Tested-by: Andrey Konovalov <andreyknvl.com>
Should be: Tested-by: Andrey Konovalov <andreyk...@google.com> > >> >> Reported-by: Andrey Konovalov <andreyk...@google.com> >> Cc: Andrey Konovalov <andreyk...@google.com> >> Signed-off-by: Cong Wang <xiyou.wangc...@gmail.com> >> --- >> net/ipv6/sit.c | 2 +- >> 1 file changed, 1 insertion(+), 1 deletion(-) >> >> diff --git a/net/ipv6/sit.c b/net/ipv6/sit.c >> index 2378503..f8ad158 100644 >> --- a/net/ipv6/sit.c >> +++ b/net/ipv6/sit.c >> @@ -305,7 +305,7 @@ static int ipip6_tunnel_get_prl(struct ip_tunnel *t, >> * we try harder to allocate. >> */ >> kp = (cmax <= 1 || capable(CAP_NET_ADMIN)) ? >> - kcalloc(cmax, sizeof(*kp), GFP_KERNEL) : >> + kcalloc(cmax, sizeof(*kp), GFP_KERNEL | __GFP_NOWARN) : >> NULL; >> >> rcu_read_lock(); >> -- >> 2.5.5 >>
