[ovs-dev] oops in if_nlmsg_size

Jorge Nevado jorge.nevado at ericsson.com
Thu Jan 15 13:53:35 UTC 2015


Yes, you are right Thomas.
Suse12, although issuing Kernel 3.12.28, has applied some patches including the " rtnl_link_get_slave_info_data_size" method but without the patch.

Thanks for your support.

-----Original Message-----
From: Thomas Graf [mailto:tgraf at noironetworks.com] 
Sent: miércoles, 14 de enero de 2015 18:42
To: Jorge Nevado
Cc: dev at openvswitch.org; Almudena Redondo; Raquel Rodriguez MAESO
Subject: Re: [ovs-dev] oops in if_nlmsg_size

On 01/14/15 at 04:21pm, Jorge Nevado wrote:
> Linux cots506 3.12.28-4-default #1 SMP Thu Sep 25 17:02:34 UTC 2014 
> (9879bd4) x86_64 x86_64 x86_64 GNU/Linux
> 
> We saw on another post that this situation can happen with kernel 3.14:
> http://openvswitch.org/pipermail/dev/2014-February/036401.html
> But the patch provided in that case applies to a method "rtnl_link_get_slave_info_data_size" that does not exist on 3.12.28.

The oops looks very much like this bug. Is it possible that SUSE backported "rtnetlink: provide api for getting and setting slave info"
but not the follow up fix?

In general, the bug does not look like its caused by OVS. OVS is merely the trigger for the netdevice notification which causes the construction of a Netlink message in this case.

I'd check with your distribution first.



More information about the dev mailing list