Ubuntu 22.04 support

[glass-hash]

This pull request adds support for Ubuntu 22.04 in BESS. Fixes #1056. Overview of the changes made:

• Fixed g++-11 (default in Ubuntu 22.04) warnings in core/modules/l2_forward.cc (-Werror=maybe-uninitialized), core/utils/exact_match_table.h (-Werror=nonnull).
• Updated DPDK 19.11 for newer kernels (Ubuntu 22.04 uses either 5.15 or 6.8 by default):
  • deps/linux_5_9.patch: Kernel v5.9 removed the task_struct pointer from get_user_pages_remote. Updated kernel/linux/kni/kni_dev.h with newer get_user_pages_remote and fixed a fallthrough warning (-Wimplicit-fallthrough) in kernel/linux/igb/igb_uio.c.
  • build.py: Now checking for version greater than or equal to 5.9 and applying the above patch. These changes depend on the packaging module in python3.
• Upgraded to python3 (default in Ubuntu 22.04):
  • bessctl/sugar.py: parser module is not present in python v3.10. Made changes to use the ast module instead.
• Updated core/Makefile: Now linking libpcap, and libgrpc++ dynamically. Statically linking them results in issues due to change in dependencies in Ubuntu 22.04. libpcap depends on libdbus and libsystemd. libsystemd does not have a static library as part of its package. Linking libgrpc++ statically results in unresolved libssl symbols, potentially due to a version mismatch in Ubuntu 22.04's libssl and the one libgrpc++ was written with.
• Modified core/kmod/sn_ethtool.c to include ethtool.h for struct ethtool_drvinfo. While the code compiles successfully on older kernel versions (Ubuntu 18.04) without this include, Ubuntu 22.04 reports 'invalid use of undefined type struct ethtool_drvinfo'. Now including ethtool.h explicitly rather than relying on transitive includes.

[prasadakhil97]

I was trying to install BESS using your repo on Ubuntu 22.04 with gcc-11. I am guessing its a kernel and gcc version mismatch. If you could let me know any specific setting that I need to use, would be of great help.

[glass-hash]

No special configurations, I tested it on Ubuntu 22.04, kernel version 5.15 and gcc 11.4.0. The -ftrivial-auto-var-init flag was introduced in gcc-12 so it makes sense that gcc-11 does not recognize it in your case. Here are the flags being added in my case while compiling igb_uio.c in DPDK 19.11 (ftrivial-auto-var-init is not there):

gcc -Wp,-MMD,/home/kshitij/bess/deps/dpdk-19.11.4/build/build/kernel/linux/igb_uio/.igb_uio.o.d -nostdinc -isystem /usr/lib/gcc/x86_64-linux-gnu/11/include -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -I./ubuntu/include -include ./include/linux/compiler_types.h -D__KERNEL__ -fmacro-prefix-map=./= -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -fshort-wchar -fno-PIE -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Wno-format-security -std=gnu89 -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=none -m64 -falign-jumps=1 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mpreferred-stack-boundary=3 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -DCONFIG_X86_X32_ABI -Wno-sign-compare -fno-asynchronous-unwind-tables -mindirect-branch=thunk-extern -mindirect-branch-register -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -fno-jump-tables -mharden-sls=all -fno-delete-null-pointer-checks -Wno-frame-address -Wno-format-truncation -Wno-format-overflow -Wno-address-of-packed-member -O2 -fno-allow-store-data-races -Wframe-larger-than=1024 -fstack-protector-strong -Wimplicit-fallthrough=5 -Wno-main -Wno-unused-but-set-variable -Wno-unused-const-variable -fno-omit-frame-pointer -fno-optimize-sibling-calls -fno-stack-clash-protection -g -gdwarf-5 -pg -mrecord-mcount -mfentry -DCC_USING_FENTRY -falign-functions=16 -Wdeclaration-after-statement -Wvla -Wno-pointer-sign -Wno-stringop-truncation -Wno-zero-length-bounds -Wno-array-bounds -Wno-stringop-overflow -Wno-restrict -Wno-maybe-uninitialized -Wno-alloc-size-larger-than -fno-strict-overflow -fno-stack-check -fconserve-stack -Werror=date-time -Werror=incompatible-pointer-types -Werror=designated-init -Wno-packed-not-aligned -I/home/kshitij/bess/deps/dpdk-19.11.4/kernel/linux/igb_uio --param max-inline-insns-single=100 -I/home/kshitij/bess/deps/dpdk-19.11.4/build/include -Winline -Wall -Werror -include /home/kshitij/bess/deps/dpdk-19.11.4/build/include/rte_config.h -fsanitize=bounds -fsanitize=shift -fsanitize=bool -fsanitize=enum -DMODULE -DKBUILD_BASENAME='"igb_uio"' -DKBUILD_MODNAME='"igb_uio"' -D__KBUILD_MODNAME=kmod_igb_uio -c -o /home/kshitij/bess/deps/dpdk-19.11.4/build/build/kernel/linux/igb_uio/igb_uio.o /home/kshitij/bess/deps/dpdk-19.11.4/build/build/kernel/linux/igb_uio/igb_uio.c

Can you verify the DPDK config in your case?