From: Thomas Graf <tgraf@suug.ch>
To: Florian Westphal <fw@strlen.de>
Cc: Sander Eikelenboom <linux@eikelenboom.it>,
Pravin B Shelar <pshelar@nicira.com>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, dev@openvswitch.org
Subject: Re: 3.19-rc4: BUG: unable to handle kernel paging request at ffff880055f15000 ovs_packet_cmd_execute+0x1f/0x229
Date: Wed, 14 Jan 2015 13:13:14 +0000 [thread overview]
Message-ID: <20150114131314.GB564@casper.infradead.org> (raw)
In-Reply-To: <20150114130351.GB13716@breakpoint.cc>
On 01/14/15 at 02:03pm, Florian Westphal wrote:
> Thomas Graf <tgraf@suug.ch> wrote:
> > Copying ovs-dev mailing list and thus qutoing full message.
> >
> > On 01/14/15 at 01:14pm, Sander Eikelenboom wrote:
> > > Hi,
> > >
> > > I was testing 3.19-rc4 with openvswitch and encountered the splat below.
> >
> > What version of OVS are you using? Did this work properly with rc3 or
> > an older kernel?
>
> seems like it was introduced via 05da5898a96c
> (openvswitch: Add support for OVS_FLOW_ATTR_PROBE).
>
> It adds test for OVS_FLOW_ATTR_PROBE to ovs_packet_cmd_execute() but
> this function seems to only expect OVS_PACKET_ATTR_* (so we get
> out-of-bounds access)?
Absolutely, just came to the same conclusion independently. I'll send
a fix.
next prev parent reply other threads:[~2015-01-14 13:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 12:14 3.19-rc4: BUG: unable to handle kernel paging request at ffff880055f15000 ovs_packet_cmd_execute+0x1f/0x229 Sander Eikelenboom
2015-01-14 13:00 ` Thomas Graf
2015-01-14 13:03 ` Florian Westphal
2015-01-14 13:13 ` Thomas Graf [this message]
2015-01-14 13:56 ` [PATCH net] openvswitch: packet messages need their own probe attribtue Thomas Graf
2015-01-14 20:40 ` Jesse Gross
2015-01-14 21:22 ` Pravin Shelar
[not found] ` <20150114135619.GC564-FZi0V3Vbi30CUdFEqe4BF2D2FQJk+8+b@public.gmane.org>
2015-01-14 21:49 ` David Miller
2015-01-14 13:05 ` 3.19-rc4: BUG: unable to handle kernel paging request at ffff880055f15000 ovs_packet_cmd_execute+0x1f/0x229 Sander Eikelenboom
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=20150114131314.GB564@casper.infradead.org \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=dev@openvswitch.org \
--cc=fw@strlen.de \
--cc=linux@eikelenboom.it \
--cc=netdev@vger.kernel.org \
--cc=pshelar@nicira.com \
/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).