From: Dave Jones <davej@redhat.com>
To: Alexei Starovoitov <ast@plumgrid.com>
Cc: Fengguang Wu <fengguang.wu@intel.com>, LKP <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
dborkman@redhat.com
Subject: Re: [net: sock] BUG: unable to handle kernel NULL pointer dereference at 0000000000000007
Date: Wed, 10 Dec 2014 20:00:53 -0500 [thread overview]
Message-ID: <20141211010053.GA23742@redhat.com> (raw)
In-Reply-To: <CAMEtUuxexMXtvK_R7YZEvx_iyK9mAx_zrqr1bkj3PsUwoq0p5A@mail.gmail.com>
On Wed, Dec 10, 2014 at 03:51:33PM -0800, Alexei Starovoitov wrote:
> On Wed, Dec 10, 2014 at 3:29 PM, Fengguang Wu <fengguang.wu@intel.com> wrote:
> > Greetings,
> >
> > 0day kernel testing robot got the below dmesg and the first bad commit is
> >
> > net: sock: allow eBPF programs to be attached to sockets
>
> > [init] Kernel was tainted on startup. Will ignore flags that are already set.
> > [init] Started watchdog process, PID is 9354
> > [main] Main thread is alive.
> > [ 21.233581] BUG: unable to handle kernel NULL pointer dereference at 0000000000000007
> > [ 21.234709] IP: [<ffffffff8156ebda>] sk_attach_bpf+0x39/0xc2
>
> thanks for the report! syscall fuzzer is great.
> I missed an extra check. Working on a fix.
This might be the first time I've seen it trip up the bpf code iirc.
Daniel wrote some pretty nifty bpf generator code in trinity,
(net/bpf.c) that you might want to see if you can think of enhancing.
Though it might be the case that we're not even needing to do anything
that complicated to hit this particular bug..
Dave
prev parent reply other threads:[~2014-12-11 1:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 23:29 [net: sock] BUG: unable to handle kernel NULL pointer dereference at 0000000000000007 Fengguang Wu
2014-12-10 23:51 ` Alexei Starovoitov
2014-12-11 1:00 ` Dave Jones [this message]
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=20141211010053.GA23742@redhat.com \
--to=davej@redhat.com \
--cc=ast@plumgrid.com \
--cc=dborkman@redhat.com \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).