Re: [PATCH v2 net] nfc: use GFP_USER for user-controlled kmalloc
From: David Miller <davem@davemloft.net>
Date: 2016-02-24 18:45:24
Also in:
netdev
Possibly related (same subject, not in this thread)
- 2016-02-25 · Re: [PATCH v2 net] nfc: use GFP_USER for user-controlled kmalloc · Samuel Ortiz <hidden>
- 2016-02-24 · Re: [PATCH v2 net] nfc: use GFP_USER for user-controlled kmalloc · Cong Wang <hidden>
- 2016-02-24 · Re: [PATCH v2 net] nfc: use GFP_USER for user-controlled kmalloc · Samuel Ortiz <hidden>
- 2016-01-29 · Re: [PATCH v2 net] nfc: use GFP_USER for user-controlled kmalloc · Julian Calaby <hidden>
- 2016-01-29 · Re: [PATCH v2 net] nfc: use GFP_USER for user-controlled kmalloc · Eric Dumazet <hidden>
From: Cong Wang <redacted> Date: Wed, 24 Feb 2016 10:41:29 -0800
On Fri, Jan 29, 2016 at 11:24 AM, Cong Wang [off-list ref] wrote:quoted
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 <dvyukov@google.com> Cc: Lauro Ramos Venancio <redacted> Cc: Aloisio Almeida Jr <redacted> Cc: Samuel Ortiz <redacted> Signed-off-by: Cong Wang <redacted>Ping... David, this patch seems still not applied, I guess you expect NFC maintainer to take it, but this doesn't happen. Could you take it?
The NFC maintainer needs to take this, ping them explicitly if you have to. Thanks.