From: Paolo Abeni <pabeni@redhat•com>
To: Andrei Vagin <avagin@gmail•com>
Cc: Linux Kernel Network Developers <netdev@vger•kernel.org>
Subject: Re: linux-next: BUG: unable to handle kernel NULL pointer dereference in __sk_mem_raise_allocated()
Date: Tue, 15 Nov 2016 10:26:50 +0100 [thread overview]
Message-ID: <1479202010.4660.11.camel@redhat.com> (raw)
In-Reply-To: <CANaxB-yCk8hhP68L4Q2nFOJht8sqgXGGQO2AftpHs0u1xyGG5A@mail.gmail.com>
Hi,
On Mon, 2016-11-14 at 15:24 -0800, Andrei Vagin wrote:
> Our test system detected a kernel oops. Looks like a problem in the
> "udp: refactor memory accounting" series.
My fault: I missed udplite in my tests.
Thank you for reporting.
I'm fine with Eric's patch, setting both .memory_allocated
and .sysctl_mem.
We could also remove .backlog_rcv, but it's not strictly needed.
Paolo
next prev parent reply other threads:[~2016-11-15 9:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 23:24 linux-next: BUG: unable to handle kernel NULL pointer dereference in __sk_mem_raise_allocated() Andrei Vagin
2016-11-14 23:35 ` Eric Dumazet
2016-11-14 23:49 ` Eric Dumazet
2016-11-14 23:58 ` Andrei Vagin
2016-11-15 0:31 ` Eric Dumazet
2016-11-15 8:57 ` Paolo Abeni
2016-11-15 0:02 ` Andrei Vagin
2016-11-15 9:26 ` Paolo Abeni [this message]
2016-11-15 14:02 ` Eric Dumazet
2016-11-15 14:07 ` Paolo Abeni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1479202010.4660.11.camel@redhat.com \
--to=pabeni@redhat$(echo .)com \
--cc=avagin@gmail$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox