Re: [PATCH] sctp: use GFP_USER for user-controlled kmalloc

2015-12-02 Thread David Miller
From: Marcelo Ricardo Leitner Date: Mon, 30 Nov 2015 14:32:54 -0200 > Dmitry Vyukov reported that the user could trigger a kernel warning by > using a large len value for getsockopt SCTP_GET_LOCAL_ADDRS, as that > value directly affects the value used as a kmalloc() parameter. > > This patch thu

Re: [PATCH] sctp: use GFP_USER for user-controlled kmalloc

2015-12-01 Thread Daniel Borkmann
On 12/01/2015 11:46 AM, David Laight wrote: From: Marcelo Ricardo Leitner Sent: 30 November 2015 16:33 Dmitry Vyukov reported that the user could trigger a kernel warning by using a large len value for getsockopt SCTP_GET_LOCAL_ADDRS, as that value directly affects the value used as a kmalloc()

RE: [PATCH] sctp: use GFP_USER for user-controlled kmalloc

2015-12-01 Thread David Laight
From: Marcelo Ricardo Leitner > Sent: 30 November 2015 16:33 > Dmitry Vyukov reported that the user could trigger a kernel warning by > using a large len value for getsockopt SCTP_GET_LOCAL_ADDRS, as that > value directly affects the value used as a kmalloc() parameter. > > This patch thus switche

[PATCH] sctp: use GFP_USER for user-controlled kmalloc

2015-11-30 Thread Marcelo Ricardo Leitner
Dmitry Vyukov reported that the user could trigger a kernel warning by using a large len value for getsockopt SCTP_GET_LOCAL_ADDRS, as that value directly affects the value used as a kmalloc() parameter. This patch thus switches the allocation flags from all user-controllable kmalloc size to GFP_U