Re: [dpdk-dev] [PATCH v3] kni: fix possible kernel crash with va2pa

2019-07-15 Thread Thomas Monjalon
11/07/2019 09:46, Ferruh Yigit: > On 7/10/2019 9:09 PM, Ferruh Yigit wrote: > > On 6/25/2019 4:04 PM, Yangchao Zhou wrote: > >> va2pa depends on the physical address and virtual address offset of > >> current mbuf. It may get the wrong physical address of next mbuf which > >> allocated in another h

Re: [dpdk-dev] [PATCH v3] kni: fix possible kernel crash with va2pa

2019-07-11 Thread Ferruh Yigit
On 7/10/2019 9:09 PM, Ferruh Yigit wrote: > On 6/25/2019 4:04 PM, Yangchao Zhou wrote: >> va2pa depends on the physical address and virtual address offset of >> current mbuf. It may get the wrong physical address of next mbuf which >> allocated in another hugepage segment. >> >> In rte_mempool_popu

Re: [dpdk-dev] [PATCH v3] kni: fix possible kernel crash with va2pa

2019-07-10 Thread Ferruh Yigit
On 6/25/2019 4:04 PM, Yangchao Zhou wrote: > va2pa depends on the physical address and virtual address offset of > current mbuf. It may get the wrong physical address of next mbuf which > allocated in another hugepage segment. > > In rte_mempool_populate_default(), trying to allocate whole block o

[dpdk-dev] [PATCH v3] kni: fix possible kernel crash with va2pa

2019-06-25 Thread Yangchao Zhou
va2pa depends on the physical address and virtual address offset of current mbuf. It may get the wrong physical address of next mbuf which allocated in another hugepage segment. In rte_mempool_populate_default(), trying to allocate whole block of contiguous memory could be failed. Then, it would r