On 3/31/2021 3:15 PM, Lynch, Daniel wrote:
Hi Greg,
Our kernel version is 4.9.175. According to the chart on the Releases page,
Open vSwitch 2.7.1 should be compatible, but compatibility ends at 4.9.x, so...
maybe not?
Daniel,
For a handful of versions of Linux from 4.10 through 4.16 there was this
member of the inet_frags struct named 'rnd'.
https://elixir.bootlin.com/linux/v4.10/source/include/net/inet_frag.h#L79
By 4.17 it was gone.
https://elixir.bootlin.com/linux/v4.17.19/A/ident/inet_frags
And I didn't find any reference to the 'rnd' inet_frags
struct member in any 4.9 kernel that I could find. That
makes it puzzling that you're seeing this error in 4.9.175.
I didn't see it in the standard Linux version but maybe your
kernel has been customized.
https://elixir.bootlin.com/linux/v4.9.175/source/include/net/inet_frag.h#L92
Openvswitch should be checking for this and defining
'HAVE_INET_FRAGS_RND' if so. Check the generated kcomat.h
header file to see if it is defined or not. That compile
switch should be wrapping all references to inet_frags.rnd.
You can find the code that defines 'HAVE_INET_FRAGS_RND' in
./acinclude.m4.
- Greg
Thanks,
Dan
On 3/31/21, 4:05 PM, "Gregory Rose" <gvrose8...@gmail.com> wrote:
CAUTION: The e-mail below is from an external source. Please exercise
caution before opening attachments, clicking links, or following guidance.
On 3/30/2021 2:11 PM, Lynch, Daniel wrote:
> This is a long shot, but I'm hoping that someone will have some insight
for an issue that we are encountering. We are using an older version of Open
vSwitch (2.7.1) with LEDE 17.01 on the Atom processor of a Puma7 SoC (MaxLinear
SDK R7.2.1), and are using Open vSwitch 2.7.1. Yocto build environment.
>
> Unfortunately, we don’t have the control to upgrade to the latest
version of OpenWrt, and with the kernel we have, we can only get Open vSwitch
2.7.1 or 2.7.3 to compile. Attempts to compile with version 2.15 fails with error:
'struct inet_frags' has no member named 'rnd'.
Hi Daniel,
What version of the Linux kernel are you building openvswitch against?
It looks like a kernel compatiblity issue.
Thanks,
- Greg
> We need to use the openvswitch.ko and vport*.ko kernel modules to bring
up ovs bridges, so we have enabled the lines
> EXTRA_OECONF = "--with-linux=${STAGING_KERNEL_DIR}
KARCH=${TARGET_ARCH}"
> in openvswitch_git.bb and openvswitch.inc.
>
> We have ovs bridges br-wan and br-home set up, and they get IP addresses
assigned during bootup. But when the Intel Logger starts up, it reports several
segfaults, and we lose connectivity with the backhaul. After that, we periodically
get reports of segfaults in liblogger.so (the Intel logger library).
>
> We found that the default gateway gets cleared whenever this segfault in
the logger occurs. If we set it back up, we have WAN connectivity again, but only
until the next time the logger segfaults.
>
> I’m asking about this here because the segfaults occur only when
openvswitch.ko is loaded. If we unload it, the segfaults stop.
>
> Does anyone have any suggestions as to how we can resolve this?
>
> Dan Lynch
> E-MAIL CONFIDENTIALITY NOTICE:
> The contents of this e-mail message and any attachments are intended
solely for the addressee(s) and may contain confidential and/or legally privileged
information. If you are not the intended recipient of this message or if this
message has been addressed to you in error, please immediately alert the sender by
reply e-mail and then delete this message and any attachments. If you are not the
intended recipient, you are notified that any use, dissemination, distribution,
copying, or storage of this message or any attachment is strictly prohibited.
> _______________________________________________
> dev mailing list
> d...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-dev
>
E-MAIL CONFIDENTIALITY NOTICE:
The contents of this e-mail message and any attachments are intended solely for
the addressee(s) and may contain confidential and/or legally privileged
information. If you are not the intended recipient of this message or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message and any attachments. If you are
not the intended recipient, you are notified that any use, dissemination,
distribution, copying, or storage of this message or any attachment is strictly
prohibited.
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
