Re: [ovs-dev] [PATCH] netdev-afxdp: Fix umem creation failure due to uninitialized config.

2019-10-11 Thread William Tu
On Fri, Oct 11, 2019 at 01:16:55PM +0200, Ilya Maximets wrote: > On 10.10.2019 20:21, William Tu wrote: > >On Wed, Oct 09, 2019 at 04:17:58PM +0200, Ilya Maximets wrote: > >>Later version of 'struct xsk_umem_config' contains additional field > >>'flags'. OVS doesn't use that field passing

Re: [ovs-dev] [PATCH] netdev-afxdp: Fix umem creation failure due to uninitialized config.

2019-10-11 Thread Ilya Maximets
On 10.10.2019 20:21, William Tu wrote: On Wed, Oct 09, 2019 at 04:17:58PM +0200, Ilya Maximets wrote: Later version of 'struct xsk_umem_config' contains additional field 'flags'. OVS doesn't use that field passing uninitialized stack memory to the 'xsk_umem__create()' call that could fail with

Re: [ovs-dev] [PATCH] netdev-afxdp: Fix umem creation failure due to uninitialized config.

2019-10-10 Thread William Tu
On Wed, Oct 09, 2019 at 04:17:58PM +0200, Ilya Maximets wrote: > Later version of 'struct xsk_umem_config' contains additional field > 'flags'. OVS doesn't use that field passing uninitialized stack > memory to the 'xsk_umem__create()' call that could fail with > 'Invalid argument' if 'flags' are

[ovs-dev] [PATCH] netdev-afxdp: Fix umem creation failure due to uninitialized config.

2019-10-09 Thread Ilya Maximets
Later version of 'struct xsk_umem_config' contains additional field 'flags'. OVS doesn't use that field passing uninitialized stack memory to the 'xsk_umem__create()' call that could fail with 'Invalid argument' if 'flags' are non-zero or, even worse, create umem with unexpected properties. We