Hi all,
In fact, I really boot my build node after upgrade kernel.
I did some investigation
1. For below error:
In file included from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/../datapath/linux/compat/include/net/gre.h:10:0,
from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/datapath/linux/vport-gre.c:44:
include/net/gre.h: In function 'gre_handle_offloads':
include/net/gre.h:42:2: error: implicit declaration of function
'iptunnel_handle_offloads' [-Werror=implicit-f
unction-declaration]
return iptunnel_handle_offloads(skb, gre_csum, SKB_GSO_GRE);
^
include/net/gre.h:42:2: warning: return makes pointer from integer without
a cast [enabled by default]
cc1: some warnings being treated as errors
I checked method iptunnel_handle_offloads which declare it in
net/ip_tunnels.h
#ifdef CONFIG_INET
...
struct sk_buff *iptunnel_handle_offloads(struct sk_buff *skb, bool
gre_csum,
...
#endif /* CONFIG_INET */
I really can find its declaration in above head file.
But seemed CONFIG_INET not defined in kernel.
Then I go to /boot to check CONFIG_INET seemed already defined there
[root@vs260 boot]# grep CONFIG_INET config-3.10.0-123.8.1.el7.x86_64 |more
CONFIG_INET=y
CONFIG_INET_AH=m
CONFIG_INET_ESP=m
CONFIG_INET_IPCOMP=m
CONFIG_INET_XFRM_TUNNEL=m
CONFIG_INET_TUNNEL=m
CONFIG_INET_XFRM_MODE_TRANSPORT=m
CONFIG_INET_XFRM_MODE_TUNNEL=m
CONFIG_INET_XFRM_MODE_BEET=m
CONFIG_INET_LRO=y
CONFIG_INET_DIAG=m
CONFIG_INET_TCP_DIAG=m
CONFIG_INET_UDP_DIAG=m
CONFIG_INET6_AH=m
CONFIG_INET6_ESP=m
CONFIG_INET6_IPCOMP=m
CONFIG_INET6_XFRM_TUNNEL=m
CONFIG_INET6_TUNNEL=m
CONFIG_INET6_XFRM_MODE_TRANSPORT=m
CONFIG_INET6_XFRM_MODE_TUNNEL=m
CONFIG_INET6_XFRM_MODE_BEET=m
CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION=m
CONFIG_INET_DCCP_DIAG=m
So I want to know if when I build, some parameters needed ?
2. For below error
In file included from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/datapath/linux/datapath.c:52:0:
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/../datapath/linux/compat/include/net/genetlink.h:100:31:
error:
static declaration of 'genlmsg_new_unicast' follows non-static declaration
static inline struct sk_buff *genlmsg_new_unicast(size_t payload,
^
In file included from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/../datapath/linux/compat/include/net/genetlink.h:7:0
,
from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/datapath/linux/datapath.c:52:
include/net/genetlink.h:162:17: note: previous declaration of
'genlmsg_new_unicast' was here
struct sk_buff *genlmsg_new_unicast(size_t payload, struct genl_info
*info,
^
In file included from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/datapath/linux/dp_notify.c:20:0:
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/../datapath/linux/compat/include/net/genetlink.h:100:31:
error:
static declaration of 'genlmsg_new_unicast' follows non-static declaration
static inline struct sk_buff *genlmsg_new_unicast(size_t payload,
^
In file included from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/../datapath/linux/compat/include/net/genetlink.h:7:0
,
from
/home/xugang/tmp3/ovs-2.3/BUILD/openvswitch-2.3.0/_default/datapath/linux/dp_notify.c:20:
include/net/genetlink.h:162:17: note: previous declaration of
'genlmsg_new_unicast' was here
struct sk_buff *genlmsg_new_unicast(size_t payload, struct genl_info
*info,
I checked our kernel which do not have static incline. Is that source
commit solved this problem?
3. What else info you need to help to debug?
Thanks
From: Flavio Leitner <f...@redhat.com>
To: Gang U Xu/China/IBM@IBMCN
Cc: Alex Wang <al...@nicira.com>, b...@openvswitch.org
Date: 2014/10/29 20:09
Subject: Re: [ovs-discuss] ovs 2.3 kernel module build failed on
rhel 7.0 GA
On Wed, Oct 29, 2014 at 03:31:03PM +0800, Gang U Xu wrote:
> Hi all,
>
> Thanks your quick support first!
>
> I did below
> 1. Update kernel to 3.10.0-123.8.1.el7.x86_64
> 2. I cherry-pick 4ae2b2c1c4c345d0cb5f5a6b0f20fd6afb4a6962 from branch
2.3,
> then generate one patch
> 3. After install patch, build again, the problem skb_zerocopy solved
now,
> but still failed for below
Not sure about the specific steps you did, but I think you need to
bootstrap the tree (./boot) again to make the changes effective.
fbl
_______________________________________________
discuss mailing list
discuss@openvswitch.org
http://openvswitch.org/mailman/listinfo/discuss
