← Back to team overview

group.of.nepali.translators team mailing list archive

[Bug 1811819] Re: please include the kernel module VXLAN

 

This bug was fixed in the package linux-kvm - 5.3.0-1003.3

---------------
linux-kvm (5.3.0-1003.3) eoan; urgency=medium

  * eoan/linux-kvm: 5.3.0-1003.3 -proposed tracker (LP: #1847294)

  * Miscellaneous Ubuntu changes
    - [Config] Enable some test modules needed for kernel selftests

  [ Ubuntu: 5.3.0-18.19 ]

  * eoan/linux: 5.3.0-18.19 -proposed tracker (LP: #1847298)
  * Enable the Dragonboards out of Eoan/master arm64 kernel (LP: #1846704)
    - [Packaging] arm64: snapdragon: introduce a snapdragon flavour
    - [Packaging] arm64: snapdragon: switch kernel format to Image
    - [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8916=y
    - [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8994=y
    - [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8996=y
    - [Config] arm64: snapdragon: CONFIG_PINCTRL_MSM8998=y
    - [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_RPMH=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_BAM_DMA=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA_MGMT=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_HIDMA=y
    - [Config] arm64: snapdragon: CONFIG_COMMON_CLK_QCOM=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_CLK_RPMH=y
    - [Config] arm64: snapdragon: CONFIG_MSM_GCC_8916=y
    - [Config] arm64: snapdragon: CONFIG_MSM_GCC_8994=y
    - [Config] arm64: snapdragon: CONFIG_MSM_MMCC_8996=y
    - [Config] arm64: snapdragon: CONFIG_MSM_GCC_8998=y
    - [Config] arm64: snapdragon: CONFIG_HWSPINLOCK_QCOM=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_APCS_IPC=y
    - [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_GLINK_RPM=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_GENI_SE=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_SMEM=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_SMD_RPM=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_SMP2P=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_SMSM=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_QFPROM=y
    - [Config] arm64: snapdragon: CONFIG_SERIAL_QCOM_GENI=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_TSENS=y
    - [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SMD_RPM=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_CLK_SMD_RPM=y
    - [Config] arm64: snapdragon: CONFIG_RPMSG_QCOM_SMD=y
    - [Config] arm64: snapdragon: CONFIG_MFD_QCOM_RPM=y
    - [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD=y
    - [Config] arm64: snapdragon: CONFIG_SCSI_UFSHCD_PLATFORM=y
    - [Config] arm64: snapdragon: CONFIG_SCSI_UFS_HISI=y
    - [Config] arm64: snapdragon: CONFIG_MMC_SDHCI=y
    - [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_PLTFM=y
    - [Config] arm64: snapdragon: CONFIG_MMC_SDHCI_MSM=y
    - [Config] arm64: snapdragon: CONFIG_REGULATOR_QCOM_SPMI=y
    - [Config] arm64: snapdragon: CONFIG_PINCTRL_QCOM_SPMI_PMIC=y
    - [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HS=y
    - [Config] arm64: snapdragon: CONFIG_PHY_QCOM_QMP=y
    - [Config] arm64: snapdragon: CONFIG_PHY_QCOM_UFS=y
    - [Config] arm64: snapdragon: CONFIG_PHY_QCOM_USB_HSIC=y
    - [Config] arm64: snapdragon: CONFIG_USB_CHIPIDEA_OF=y
    - [Config] arm64: snapdragon: CONFIG_USB_EHCI_HCD_PLATFORM=y
    - [Config] arm64: snapdragon: CONFIG_EXTCON_USB_GPIO=y
    - [Config] arm64: snapdragon: CONFIG_REGULATOR_FIXED_VOLTAGE=y
    - [Config] arm64: snapdragon: CONFIG_LEDS_GPIO=y
    - [Config] arm64: snapdragon: CONFIG_USB_HSIC_USB3503=y
    - [Config] arm64: snapdragon: CONFIG_USB_NET_DRIVERS=y
    - [Config] arm64: snapdragon: CONFIG_USB_OTG=y
    - [Config] arm64: snapdragon: CONFIG_USB_XHCI_PLATFORM=y
    - [Config] arm64: snapdragon: CONFIG_USB_OHCI_HCD_PLATFORM=y
    - [Config] arm64: snapdragon: CONFIG_USB_MUSB_HDRC=y
    - [Config] arm64: snapdragon: CONFIG_USB_DWC3=y
    - [Config] arm64: snapdragon: CONFIG_USB_DWC3_PCI=y
    - [Config] arm64: snapdragon: CONFIG_USB_DWC3_OF_SIMPLE=y
    - [Config] arm64: snapdragon: CONFIG_USB_DWC3_QCOM=y
    - [Config] arm64: snapdragon: CONFIG_LEDS_PWM=y
    - [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_HEARTBEAT=y
    - [Config] arm64: snapdragon: CONFIG_LEDS_TRIGGER_DEFAULT_ON=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_A53PLL=y
    - [Config] arm64: snapdragon: CONFIG_QCOM_CLK_APCS_MSM8916=y
    - [Config] arm64: snapdragon: CONFIG_NLS_ISO8859_1=y
    - [Config] arm64: snapdragon: CONFIG_USB_USBNET=y
    - [Config] arm64: snapdragon: CONFIG_CRYPTO_DEV_QCOM_RNG=y
    - [Config] arm64: snapdragon: CONFIG_POWER_RESET_QCOM_PON=y
    - [Config] arm64: snapdragon: CONFIG_INPUT_PM8941_PWRKEY=y
    - [Config] arm64: snapdragon: CONFIG_KEYBOARD_GPIO=y
    - [Config] arm64: snapdragon: CONFIG_RTC_DRV_PM8XXX=y

  [ Ubuntu: 5.3.0-17.18 ]

  * eoan/linux: 5.3.0-17.18 -proposed tracker (LP: #1846641)
  * CVE-2019-17056
    - nfc: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-17055
    - mISDN: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-17054
    - appletalk: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-17053
    - ieee802154: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-17052
    - ax25: enforce CAP_NET_RAW for raw sockets
  * CVE-2019-15098
    - ath6kl: fix a NULL-ptr-deref bug in ath6kl_usb_alloc_urb_from_pipe()
  * xHCI on AMD Stoney Ridge cannot detect USB 2.0 or 1.1 devices.
    (LP: #1846470)
    - x86/PCI: Avoid AMD FCH XHCI USB PME# from D0 defect
  * Re-enable linux-libc-dev build on i386 (LP: #1846508)
    - [Packaging] Build only linux-libc-dev for i386
    - [Debian] final-checks -- ignore archtictures with no binaries
  * arm64: loop on boot after installing linux-generic-hwe-18.04-edge/bionic-
    proposed (LP: #1845820)
    - [Config] Disable CONFIG_ARM_SMMU_DISABLE_BYPASS_BY_DEFAULT
  * Revert ESE DASD discard support (LP: #1846219)
    - SAUCE: Revert "s390/dasd: Add discard support for ESE volumes"
  * Miscellaneous Ubuntu changes
    - update dkms package versions

  [ Ubuntu: 5.3.0-16.17 ]

  * eoan/linux: 5.3.0-16.17 -proposed tracker (LP: #1846204)
  * zfs fails to build on s390x  with debug symbols enabled (LP: #1846143)
    - SAUCE: s390: Mark atomic const ops always inline

 -- Seth Forshee <seth.forshee@xxxxxxxxxxxxx>  Wed, 09 Oct 2019 10:25:18
-0500

** Changed in: linux-kvm (Ubuntu)
       Status: In Progress => Fix Released

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-15098

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17052

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17053

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17054

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17055

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-17056

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1811819

Title:
  please include the kernel module VXLAN

Status in linux-kvm package in Ubuntu:
  Fix Released
Status in linux-kvm source package in Xenial:
  Fix Committed
Status in linux-kvm source package in Bionic:
  Fix Released
Status in linux-kvm source package in Disco:
  Fix Released

Bug description:
  == SRU Justification ==
  VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes,
  it will be great to enable the support in KVM kernels.

  == Fix ==
  Enable the CONFIG_VXLAN in the config file.
  CONFIG_NET_UDP_TUNNEL=m and other configs were added automatically with
  updateconfigs.

  CONFIG_OPENVSWITCH_VXLAN supprt was excluded intentionally as this is
  not requested (and to reduce the binary size).

  == Test ==
  Test kernels could be found here:
  https://people.canonical.com/~phlin/kernel/lp-1811819-vxlan/

  Kernel smoke tested.
  User has also verified that all the patched kernels are working as
  expected.

  == Regression Potentail ==
  Low, this enables the support for VXLAN module on KVM kernels, we might
  see some related bugs in the future. Since we already have this in the
  generic kernel so the impact should be small.

  
  == Original Bug Report ==
  The kernel built with this packages does have VXLAN compiled.
  It would be nice if this could be fixed since VXLAN is used by Flannel and maybe other CNI plugins for Kubernetes.

  $ grep -i vxlan /boot/config-4.4.0-1039-kvm
  # CONFIG_VXLAN is not set

  When running a kubernetes cluster with Flannel with this image:

  $ kubectl logs kube-flannel-ds-amd64-jfkc8 -n kube-system --kubeconfig=case1-admin.conf
  I0116 11:35:34.176962       1 main.go:475] Determining IP address of default interface
  I0116 11:35:34.177231       1 main.go:488] Using interface with name ens3 and address 10.32.192.14
  I0116 11:35:34.177259       1 main.go:505] Defaulting external address to interface address (10.32.192.14)
  I0116 11:35:34.191358       1 kube.go:131] Waiting 10m0s for node controller to sync
  I0116 11:35:34.273844       1 kube.go:294] Starting kube subnet manager
  I0116 11:35:35.274075       1 kube.go:138] Node controller sync successful
  I0116 11:35:35.274106       1 main.go:235] Created subnet manager: Kubernetes Subnet Manager - node-1-case1
  I0116 11:35:35.274113       1 main.go:238] Installing signal handlers
  I0116 11:35:35.274233       1 main.go:353] Found network config - Backend type: vxlan
  I0116 11:35:35.274292       1 vxlan.go:120] VXLAN config: VNI=1 Port=0 GBP=false DirectRouting=false
  E0116 11:35:35.275803       1 main.go:280] Error registering network: operation not supported
  I0116 11:35:35.275860       1 main.go:333] Stopping shutdownHandler...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1811819/+subscriptions