Return-path: Received: from mail-io0-f194.google.com ([209.85.223.194]:36098 "EHLO mail-io0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757040AbcA2WCQ (ORCPT ); Fri, 29 Jan 2016 17:02:16 -0500 MIME-Version: 1.0 In-Reply-To: <1454096764.7627.66.camel@edumazet-glaptop2.roam.corp.google.com> References: <1454095465-16685-1-git-send-email-xiyou.wangcong@gmail.com> <1454096764.7627.66.camel@edumazet-glaptop2.roam.corp.google.com> From: Julian Calaby Date: Sat, 30 Jan 2016 09:01:56 +1100 Message-ID: (sfid-20160129_230221_326231_40AF8D97) Subject: Re: [PATCH v2 net] nfc: use GFP_USER for user-controlled kmalloc To: Cong Wang Cc: netdev , Dmitry Vyukov , Eric Dumazet , linux-wireless , Lauro Ramos Venancio , Aloisio Almeida Jr , Samuel Ortiz Content-Type: text/plain; charset=UTF-8 Sender: linux-wireless-owner@vger.kernel.org List-ID: Hi Cong On Sat, Jan 30, 2016 at 6:46 AM, Eric Dumazet wrote: > On Fri, 2016-01-29 at 11:24 -0800, Cong Wang wrote: >> These two functions are called in sendmsg path, and the >> 'len' is passed from user-space, so we should not allow >> malicious users to OOM kernel on purpose. >> >> Reported-by: Dmitry Vyukov >> Cc: Lauro Ramos Venancio >> Cc: Aloisio Almeida Jr >> Cc: Samuel Ortiz >> Signed-off-by: Cong Wang >> --- > > Note that the issue is not OOM the kernel (as the allocation is > attempted even after your patch), but having a way to > spill stack traces in the syslog. > > Acked-by: Eric Dumazet Reviewed-by: Julian Calaby Thanks, -- Julian Calaby Email: julian.calaby@gmail.com Profile: http://www.google.com/profiles/julian.calaby/