[linux-yocto] [PATCH] iommu/iova: Init the struct iova to fix the possible memleak

2019-12-12 Thread Xiaotao Yin
8 The reason: When alloc_iova_mem() without initial with Zero, sometimes fpn_lo will equal to IOVA_ANCHOR by chance, so when return with -ENOMEM(iova32_full) from __alloc_and_insert_iova_range(), the new_iova will not be freed in free_iova_mem(). Fixes: bb68b2fbfbd6 ("iommu/iova: Add rbtree ancho

[linux-yocto] [PATCH] net: octeontx2-pf: Don't set the parse mode for LBKs

2019-12-12 Thread Xiaotao Yin
From: Kevin Hao The LBKs are not allowed to set the parse mode. It will return an error if we try to do so, then cause a failure when opening these ports. Signed-off-by: Kevin Hao Signed-off-by: Xiaotao Yin --- drivers/net/ethernet/marvell/octeontx2/nic/otx2_pf.c | 10 ++ 1 file

Re: [linux-yocto] [PATCH] iommu/iova: kmemleak when pfn_lo equal IOVA_ANCHOR

2019-12-08 Thread Xiaotao Yin
I Forget some information, please ignore this one, I'll send another one instead. Thanks. Br. -Original Message- From: linux-yocto@lists.yoctoproject.org On Behalf Of Xiaotao Yin Sent: Monday, December 9, 2019 1:55 PM To: linux-yocto@lists.yoctoproject.org; bruce.ashfi...@gmail.com

[linux-yocto] [PATCH] iommu/iova: kmemleak when pfn_lo equal IOVA_ANCHOR

2019-12-08 Thread Xiaotao Yin
During ethernet(Marvell octeontx2) set ring buffer test: ethtool -G eth1 rx tx following kmemleak will happen sometimes: unreferenced object 0x000b85421340 (size 64): comm "ethtool", pid 867, jiffies 4295323539 (age 550.500s) hex dump (first 64 bytes): 80 13 42 85 0b 00 ff ff ff ff

[linux-yocto] Review request [CD][BSP]marvell_cn96xx - upgrade to kernel v5.4

2019-11-27 Thread Xiaotao Yin
esources octeontx2-af: Handle physical link state change requests Vidhya Vidhyaraman (1): octeontx2-af: Add programmed macaddr to RVU pfvf Vidya Velumuri (1): octeontx2-af: Support to enable/disable Inline Ipsec functionality Xiaotao Yin (1): irq/irqdomain: Fix kmemleak in i