netdev - Re: linux-next: BUG: unable to handle kernel NULL pointer dereference in __sk_mem_raise

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1479169886.8455.111.camel@edumazet-glaptop3.roam.corp.google.com>
Date:   Mon, 14 Nov 2016 16:31:26 -0800
From:   Eric Dumazet <eric.dumazet@...il.com>
To:     Andrei Vagin <avagin@...il.com>
Cc:     Linux Kernel Network Developers <netdev@...r.kernel.org>,
        Paolo Abeni <pabeni@...hat.com>
Subject: Re: linux-next: BUG: unable to handle kernel NULL pointer
 dereference in __sk_mem_raise_allocated()

On Mon, 2016-11-14 at 15:58 -0800, Andrei Vagin wrote:

> 
> Yes, you are right. It works if we set .memory_allocated and .sysctl_mem.

Now the question would be :

Are we okay if UDP and UDPlite share the same limits ?

I would vote for yes, because these default limits are huge anyway
(The 50% reduction done in
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b66e91ccbc34ebd5a2f90f9e1bc1597e2924a500
only impacted TCP )