Bug#971277: dpdk 18.11.10-1~deb10u1 flagged for acceptance
On Mon, 2020-10-26 at 17:56 +, Adam D. Barratt wrote: > On Mon, 2020-10-26 at 15:18 +, Luca Boccassi wrote: > > On Sun, 2020-10-25 at 12:11 +, Luca Boccassi wrote: > > > On Sat, 24 Oct 2020 at 18:38, Adam D. Barratt < > > > a...@adam-barratt.org.uk> wrote: > [...] > > > > Unfortunately, this FTBFS on armhf (in three attempts across two > > > > different buildds): > [...] > > I found the issue, and I have a patch ready (a mainline commit was > > mistakenly not tagged for backport). Also found that the armv7 CI was > > disabled due to infra issues - I'll fix that too. > > Cool, thanks for the quick turnaround. > > > In terms of process, how do I proceed? A deb10u2 upload to stable? > > Yes, as the archive already contains ~deb10u1. > > > Do I need to create a new bug? > > As this is a build fix for the upload tracked by this bug, then > continuing to use this bug is fine in this instance. If it were a new > set of changes then it should be tracked in a separate bug. > > Please do attach an updated debdiff to this bug though. > > Regards, > > Adam Uploaded and debdiff attached. Tested the build on the harris armhf porterbox. -- Kind regards, Luca Boccassi diff -Nru dpdk-18.11.10/debian/changelog dpdk-18.11.10/debian/changelog --- dpdk-18.11.10/debian/changelog 2020-09-28 15:35:37.0 +0100 +++ dpdk-18.11.10/debian/changelog 2020-10-26 10:44:57.0 + @@ -1,3 +1,9 @@ +dpdk (18.11.10-1~deb10u2) buster; urgency=medium + + * Backport patch to fix armhf build with NEON + + -- Luca Boccassi Mon, 26 Oct 2020 10:44:57 + + dpdk (18.11.10-1~deb10u1) buster; urgency=medium * New upstream version 18.11.10 diff -Nru dpdk-18.11.10/debian/patches/0008-net-i40e-support-aarch32.patch dpdk-18.11.10/debian/patches/0008-net-i40e-support-aarch32.patch --- dpdk-18.11.10/debian/patches/0008-net-i40e-support-aarch32.patch 1970-01-01 01:00:00.0 +0100 +++ dpdk-18.11.10/debian/patches/0008-net-i40e-support-aarch32.patch 2020-10-26 10:44:57.0 + @@ -0,0 +1,42 @@ +Author: Ruifeng Wang +Origin: https://git.dpdk.org/dpdk/commit/?id=78bfe1666b2063e3fc3fa51e757159f53e1fc779 +Description: fix armhf build with NEON +--- a/config/defconfig_arm-armv7a-linuxapp-gcc b/config/defconfig_arm-armv7a-linuxapp-gcc +@@ -45,7 +45,6 @@ CONFIG_RTE_LIBRTE_CXGBE_PMD=n + CONFIG_RTE_LIBRTE_E1000_PMD=n + CONFIG_RTE_LIBRTE_ENIC_PMD=n + CONFIG_RTE_LIBRTE_FM10K_PMD=n +-CONFIG_RTE_LIBRTE_I40E_PMD=n + CONFIG_RTE_LIBRTE_IXGBE_PMD=n + CONFIG_RTE_LIBRTE_MLX4_PMD=n + CONFIG_RTE_LIBRTE_VMXNET3_PMD=n +--- a/drivers/net/i40e/Makefile b/drivers/net/i40e/Makefile +@@ -74,7 +74,7 @@ SRCS-$(CONFIG_RTE_LIBRTE_I40E_PMD) += i40e_dcb.c + + SRCS-$(CONFIG_RTE_LIBRTE_I40E_PMD) += i40e_ethdev.c + SRCS-$(CONFIG_RTE_LIBRTE_I40E_PMD) += i40e_rxtx.c +-ifeq ($(CONFIG_RTE_ARCH_ARM64),y) ++ifneq ($(filter y,$(CONFIG_RTE_ARCH_ARM) $(CONFIG_RTE_ARCH_ARM64)),) + SRCS-$(CONFIG_RTE_LIBRTE_I40E_INC_VECTOR) += i40e_rxtx_vec_neon.c + else ifeq ($(CONFIG_RTE_ARCH_PPC_64),y) + SRCS-$(CONFIG_RTE_LIBRTE_I40E_INC_VECTOR) += i40e_rxtx_vec_altivec.c +--- a/drivers/net/i40e/i40e_rxtx_vec_neon.c b/drivers/net/i40e/i40e_rxtx_vec_neon.c +@@ -6,6 +6,7 @@ + #include + #include + #include ++#include + + #include "base/i40e_prototype.h" + #include "base/i40e_type.h" +@@ -13,7 +14,6 @@ + #include "i40e_rxtx.h" + #include "i40e_rxtx_vec_common.h" + +-#include + + #pragma GCC diagnostic ignored "-Wcast-qual" + diff -Nru dpdk-18.11.10/debian/patches/series dpdk-18.11.10/debian/patches/series --- dpdk-18.11.10/debian/patches/series 2020-09-28 15:17:35.0 +0100 +++ dpdk-18.11.10/debian/patches/series 2020-10-26 10:44:37.0 + @@ -2,3 +2,4 @@ 0005-build-use-dependency-instead-of-find_library.patch 0006-build-reorder-libraries-and-build-eal-before-cmdline.patch 0007-build-use-dependency-for-libbsd-instead-of-manual-ap.patch +0008-net-i40e-support-aarch32.patch signature.asc Description: This is a digitally signed message part
Bug#971277: dpdk 18.11.10-1~deb10u1 flagged for acceptance
On Mon, 2020-10-26 at 15:18 +, Luca Boccassi wrote: > On Sun, 2020-10-25 at 12:11 +, Luca Boccassi wrote: > > On Sat, 24 Oct 2020 at 18:38, Adam D. Barratt < > > a...@adam-barratt.org.uk> wrote: [...] > > > Unfortunately, this FTBFS on armhf (in three attempts across two > > > different buildds): [...] > I found the issue, and I have a patch ready (a mainline commit was > mistakenly not tagged for backport). Also found that the armv7 CI was > disabled due to infra issues - I'll fix that too. Cool, thanks for the quick turnaround. > In terms of process, how do I proceed? A deb10u2 upload to stable? Yes, as the archive already contains ~deb10u1. > Do I need to create a new bug? As this is a build fix for the upload tracked by this bug, then continuing to use this bug is fine in this instance. If it were a new set of changes then it should be tracked in a separate bug. Please do attach an updated debdiff to this bug though. Regards, Adam
Bug#971277: dpdk 18.11.10-1~deb10u1 flagged for acceptance
On Sun, 2020-10-25 at 12:11 +, Luca Boccassi wrote: > On Sat, 24 Oct 2020 at 18:38, Adam D. Barratt > wrote: > > On Fri, 2020-10-16 at 17:05 +, Adam D Barratt wrote: > > > Package: dpdk > > > Version: 18.11.10-1~deb10u1 > > > > > > Explanation: new upstream stable release; fix remote code execution > > > issue [CVE-2020-14374], TOCTOU issues [CVE-2020-14375], buffer > > > overflow [CVE-2020-14376], buffer over read [CVE-2020-14377] and > > > integer underflow [CVE-2020-14377] > > > > Unfortunately, this FTBFS on armhf (in three attempts across two > > different buildds): > > > > --- start log extract --- > > > > FAILED: > > drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o > > cc -Idrivers/a715181@@tmp_rte_pmd_i40e@sta -Idrivers -I../drivers > > -Idrivers/net/i40e -I../drivers/net/i40e -Idrivers/net/i40e/base > > -I../drivers/net/i40e/base -Ilib/librte_ethdev -I../lib/librte_ethdev -I. > > -I../ -Iconfig -I../config -Ilib/librte_eal/common > > -I../lib/librte_eal/common -Ilib/librte_eal/common/include > > -I../lib/librte_eal/common/include -Ilib/librte_eal/common/include/arch/arm > > -I../lib/librte_eal/common/include/arch/arm > > -I../lib/librte_eal/linuxapp/eal/include > > -Ilib/librte_eal/linuxapp/eal/../../../librte_compat > > -I../lib/librte_eal/linuxapp/eal/../../../librte_compat -Ilib/librte_eal > > -I../lib/librte_eal -Ilib/librte_kvargs/../librte_eal/common/include > > -I../lib/librte_kvargs/../librte_eal/common/include -Ilib/librte_kvargs > > -I../lib/librte_kvargs -Ilib/librte_compat -I../lib/librte_compat > > -Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf -I../lib/librte_mbuf > > -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring > > -I../lib/librte_ring -Ilib/librte_cmdline/../librte_eal/common/include > > -I../lib/librte_cmdline/../librte_eal/common/include -Ilib/librte_cmdline > > -I../lib/librte_cmdline -Idrivers/bus/pci -I../drivers/bus/pci > > -I../drivers/bus/pci/linux -Ilib/librte_pci -I../lib/librte_pci > > -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/librte_hash > > -I../lib/librte_hash -fdiagnostics-color=always -pipe > > -D_FILE_OFFSET_BITS=64 -include rte_config.h -Wsign-compare -Wcast-qual > > -Wno-pointer-to-int-cast -D_GNU_SOURCE -g -O2 > > -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat > > -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC > > -march=armv7-a -mfpu=neon -Wno-format-truncation -DPF_DRIVER -DVF_DRIVER > > -DINTEGRATED_VF -DX722_A0_SUPPORT -DALLOW_EXPERIMENTAL_API -MD -MQ > > 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o' -MF > > 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o.d' > > -o 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o' > > -c ../drivers/net/i40e/i40e_rxtx_vec_neon.c > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c: In function ‘desc_to_olflags_v’: > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:142:31: warning: implicit > > declaration of function ‘vqtbl1q_u8’; did you mean ‘vtbl1_u8’? > > [-Wimplicit-function-declaration] > > vlan0 = vreinterpretq_u32_u8(vqtbl1q_u8(vlan_flags, > >^~ > >vtbl1_u8 > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:142:31: error: incompatible type > > for argument 1 of ‘vreinterpretq_u32_u8’ > > vlan0 = vreinterpretq_u32_u8(vqtbl1q_u8(vlan_flags, > >^~ > >vreinterpretq_u8_u32(vlan1))); > > [...] > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c: In function ‘_recv_raw_pkts_vec’: > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:320:11: error: incompatible types > > when assigning to type ‘uint8x16_t’ from type ‘int’ > >pkt_mb4 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[3]), shuf_msk); > >^ > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:321:11: error: incompatible types > > when assigning to type ‘uint8x16_t’ from type ‘int’ > >pkt_mb3 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[2]), shuf_msk); > >^ > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:351:11: error: incompatible types > > when assigning to type ‘uint8x16_t’ from type ‘int’ > >pkt_mb2 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[1]), shuf_msk); > >^ > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:352:11: error: incompatible types > > when assigning to type ‘uint8x16_t’ from type ‘int’ > >pkt_mb1 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[0]), shuf_msk); > >^ > > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:383:13: error: incompatible types > > when assigning to type ‘uint8x16_t’ from type ‘int’ > > eop_bits = vqtbl1q_u8(eop_bits, eop_shuf_mask); > > > > ^ > > > > --- end log extract --- > > > > Regards, > > > > Adam > > Mh that looks familiar, I thought it was already fixed. I'll have a > look on Monday morning, and also see why the CI missed it. > > Kind regards, > Luca Boccassi I found the issue,
Bug#971277: dpdk 18.11.10-1~deb10u1 flagged for acceptance
On Sat, 24 Oct 2020 at 18:38, Adam D. Barratt wrote: > > On Fri, 2020-10-16 at 17:05 +, Adam D Barratt wrote: > > Package: dpdk > > Version: 18.11.10-1~deb10u1 > > > > Explanation: new upstream stable release; fix remote code execution > > issue [CVE-2020-14374], TOCTOU issues [CVE-2020-14375], buffer > > overflow [CVE-2020-14376], buffer over read [CVE-2020-14377] and > > integer underflow [CVE-2020-14377] > > Unfortunately, this FTBFS on armhf (in three attempts across two > different buildds): > > --- start log extract --- > > FAILED: drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o > cc -Idrivers/a715181@@tmp_rte_pmd_i40e@sta -Idrivers -I../drivers > -Idrivers/net/i40e -I../drivers/net/i40e -Idrivers/net/i40e/base > -I../drivers/net/i40e/base -Ilib/librte_ethdev -I../lib/librte_ethdev -I. > -I../ -Iconfig -I../config -Ilib/librte_eal/common -I../lib/librte_eal/common > -Ilib/librte_eal/common/include -I../lib/librte_eal/common/include > -Ilib/librte_eal/common/include/arch/arm > -I../lib/librte_eal/common/include/arch/arm > -I../lib/librte_eal/linuxapp/eal/include > -Ilib/librte_eal/linuxapp/eal/../../../librte_compat > -I../lib/librte_eal/linuxapp/eal/../../../librte_compat -Ilib/librte_eal > -I../lib/librte_eal -Ilib/librte_kvargs/../librte_eal/common/include > -I../lib/librte_kvargs/../librte_eal/common/include -Ilib/librte_kvargs > -I../lib/librte_kvargs -Ilib/librte_compat -I../lib/librte_compat > -Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf -I../lib/librte_mbuf > -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring > -I../lib/librte_ring -Ilib/librte_cmdline/../librte_eal/common/include > -I../lib/librte_cmdline/../librte_eal/common/include -Ilib/librte_cmdline > -I../lib/librte_cmdline -Idrivers/bus/pci -I../drivers/bus/pci > -I../drivers/bus/pci/linux -Ilib/librte_pci -I../lib/librte_pci > -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/librte_hash > -I../lib/librte_hash -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 > -include rte_config.h -Wsign-compare -Wcast-qual -Wno-pointer-to-int-cast > -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. > -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time > -D_FORTIFY_SOURCE=2 -fPIC -march=armv7-a -mfpu=neon -Wno-format-truncation > -DPF_DRIVER -DVF_DRIVER -DINTEGRATED_VF -DX722_A0_SUPPORT > -DALLOW_EXPERIMENTAL_API -MD -MQ > 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o' -MF > 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o.d' -o > 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o' -c > ../drivers/net/i40e/i40e_rxtx_vec_neon.c > ../drivers/net/i40e/i40e_rxtx_vec_neon.c: In function ‘desc_to_olflags_v’: > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:142:31: warning: implicit > declaration of function ‘vqtbl1q_u8’; did you mean ‘vtbl1_u8’? > [-Wimplicit-function-declaration] > vlan0 = vreinterpretq_u32_u8(vqtbl1q_u8(vlan_flags, >^~ >vtbl1_u8 > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:142:31: error: incompatible type for > argument 1 of ‘vreinterpretq_u32_u8’ > vlan0 = vreinterpretq_u32_u8(vqtbl1q_u8(vlan_flags, >^~ >vreinterpretq_u8_u32(vlan1))); > [...] > ../drivers/net/i40e/i40e_rxtx_vec_neon.c: In function ‘_recv_raw_pkts_vec’: > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:320:11: error: incompatible types > when assigning to type ‘uint8x16_t’ from type ‘int’ >pkt_mb4 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[3]), shuf_msk); >^ > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:321:11: error: incompatible types > when assigning to type ‘uint8x16_t’ from type ‘int’ >pkt_mb3 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[2]), shuf_msk); >^ > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:351:11: error: incompatible types > when assigning to type ‘uint8x16_t’ from type ‘int’ >pkt_mb2 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[1]), shuf_msk); >^ > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:352:11: error: incompatible types > when assigning to type ‘uint8x16_t’ from type ‘int’ >pkt_mb1 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[0]), shuf_msk); >^ > ../drivers/net/i40e/i40e_rxtx_vec_neon.c:383:13: error: incompatible types > when assigning to type ‘uint8x16_t’ from type ‘int’ > eop_bits = vqtbl1q_u8(eop_bits, eop_shuf_mask); > > ^ > > --- end log extract --- > > Regards, > > Adam Mh that looks familiar, I thought it was already fixed. I'll have a look on Monday morning, and also see why the CI missed it. Kind regards, Luca Boccassi
Bug#971277: dpdk 18.11.10-1~deb10u1 flagged for acceptance
On Fri, 2020-10-16 at 17:05 +, Adam D Barratt wrote: > Package: dpdk > Version: 18.11.10-1~deb10u1 > > Explanation: new upstream stable release; fix remote code execution > issue [CVE-2020-14374], TOCTOU issues [CVE-2020-14375], buffer > overflow [CVE-2020-14376], buffer over read [CVE-2020-14377] and > integer underflow [CVE-2020-14377] Unfortunately, this FTBFS on armhf (in three attempts across two different buildds): --- start log extract --- FAILED: drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o cc -Idrivers/a715181@@tmp_rte_pmd_i40e@sta -Idrivers -I../drivers -Idrivers/net/i40e -I../drivers/net/i40e -Idrivers/net/i40e/base -I../drivers/net/i40e/base -Ilib/librte_ethdev -I../lib/librte_ethdev -I. -I../ -Iconfig -I../config -Ilib/librte_eal/common -I../lib/librte_eal/common -Ilib/librte_eal/common/include -I../lib/librte_eal/common/include -Ilib/librte_eal/common/include/arch/arm -I../lib/librte_eal/common/include/arch/arm -I../lib/librte_eal/linuxapp/eal/include -Ilib/librte_eal/linuxapp/eal/../../../librte_compat -I../lib/librte_eal/linuxapp/eal/../../../librte_compat -Ilib/librte_eal -I../lib/librte_eal -Ilib/librte_kvargs/../librte_eal/common/include -I../lib/librte_kvargs/../librte_eal/common/include -Ilib/librte_kvargs -I../lib/librte_kvargs -Ilib/librte_compat -I../lib/librte_compat -Ilib/librte_net -I../lib/librte_net -Ilib/librte_mbuf -I../lib/librte_mbuf -Ilib/librte_mempool -I../lib/librte_mempool -Ilib/librte_ring -I../lib/librte_ring -Ilib/librte_cmdline/../librte_eal/common/include -I../lib/librte_cmdline/../librte_eal/common/include -Ilib/librte_cmdline -I../lib/librte_cmdline -Idrivers/bus/pci -I../drivers/bus/pci -I../drivers/bus/pci/linux -Ilib/librte_pci -I../lib/librte_pci -Idrivers/bus/vdev -I../drivers/bus/vdev -Ilib/librte_hash -I../lib/librte_hash -fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -include rte_config.h -Wsign-compare -Wcast-qual -Wno-pointer-to-int-cast -D_GNU_SOURCE -g -O2 -fdebug-prefix-map=/<>=. -fstack-protector-strong -Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC -march=armv7-a -mfpu=neon -Wno-format-truncation -DPF_DRIVER -DVF_DRIVER -DINTEGRATED_VF -DX722_A0_SUPPORT -DALLOW_EXPERIMENTAL_API -MD -MQ 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o' -MF 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o.d' -o 'drivers/a715181@@tmp_rte_pmd_i40e@sta/net_i40e_i40e_rxtx_vec_neon.c.o' -c ../drivers/net/i40e/i40e_rxtx_vec_neon.c ../drivers/net/i40e/i40e_rxtx_vec_neon.c: In function ‘desc_to_olflags_v’: ../drivers/net/i40e/i40e_rxtx_vec_neon.c:142:31: warning: implicit declaration of function ‘vqtbl1q_u8’; did you mean ‘vtbl1_u8’? [-Wimplicit-function-declaration] vlan0 = vreinterpretq_u32_u8(vqtbl1q_u8(vlan_flags, ^~ vtbl1_u8 ../drivers/net/i40e/i40e_rxtx_vec_neon.c:142:31: error: incompatible type for argument 1 of ‘vreinterpretq_u32_u8’ vlan0 = vreinterpretq_u32_u8(vqtbl1q_u8(vlan_flags, ^~ vreinterpretq_u8_u32(vlan1))); [...] ../drivers/net/i40e/i40e_rxtx_vec_neon.c: In function ‘_recv_raw_pkts_vec’: ../drivers/net/i40e/i40e_rxtx_vec_neon.c:320:11: error: incompatible types when assigning to type ‘uint8x16_t’ from type ‘int’ pkt_mb4 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[3]), shuf_msk); ^ ../drivers/net/i40e/i40e_rxtx_vec_neon.c:321:11: error: incompatible types when assigning to type ‘uint8x16_t’ from type ‘int’ pkt_mb3 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[2]), shuf_msk); ^ ../drivers/net/i40e/i40e_rxtx_vec_neon.c:351:11: error: incompatible types when assigning to type ‘uint8x16_t’ from type ‘int’ pkt_mb2 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[1]), shuf_msk); ^ ../drivers/net/i40e/i40e_rxtx_vec_neon.c:352:11: error: incompatible types when assigning to type ‘uint8x16_t’ from type ‘int’ pkt_mb1 = vqtbl1q_u8(vreinterpretq_u8_u64(descs[0]), shuf_msk); ^ ../drivers/net/i40e/i40e_rxtx_vec_neon.c:383:13: error: incompatible types when assigning to type ‘uint8x16_t’ from type ‘int’ eop_bits = vqtbl1q_u8(eop_bits, eop_shuf_mask); ^ --- end log extract --- Regards, Adam
Bug#971277: dpdk 18.11.10-1~deb10u1 flagged for acceptance
package release.debian.org tags 971277 = buster pending thanks Hi, The upload referenced by this bug report has been flagged for acceptance into the proposed-updates queue for Debian buster. Thanks for your contribution! Upload details == Package: dpdk Version: 18.11.10-1~deb10u1 Explanation: new upstream stable release; fix remote code execution issue [CVE-2020-14374], TOCTOU issues [CVE-2020-14375], buffer overflow [CVE-2020-14376], buffer over read [CVE-2020-14377] and integer underflow [CVE-2020-14377]
