Re: [PATCH] test/argparse: fix out of bound memcpy

2025-07-06 Thread fengchengwen
Acked-by: Chengwen Feng On 2025/6/28 0:22, Stephen Hemminger wrote: > The rte_argparse API use variable length arrays for the args. > But the test was only putting space on stack for the argparse > part, not the args. This can lead to out of bounds writes. > > The bug only gets detected if DPDK

Re: [PATCH] test/argparse: fix out of bound memcpy

2025-06-30 Thread Stephen Hemminger
On Fri, 27 Jun 2025 19:56:57 +0100 Bruce Richardson wrote: > On Fri, Jun 27, 2025 at 09:22:35AM -0700, Stephen Hemminger wrote: > > The rte_argparse API use variable length arrays for the args. > > But the test was only putting space on stack for the argparse > > part, not the args. This can lead

Re: [PATCH] test/argparse: fix out of bound memcpy

2025-06-27 Thread Bruce Richardson
On Fri, Jun 27, 2025 at 09:22:35AM -0700, Stephen Hemminger wrote: > The rte_argparse API use variable length arrays for the args. > But the test was only putting space on stack for the argparse > part, not the args. This can lead to out of bounds writes. > > The bug only gets detected if DPDK is

[PATCH] test/argparse: fix out of bound memcpy

2025-06-27 Thread Stephen Hemminger
The rte_argparse API use variable length arrays for the args. But the test was only putting space on stack for the argparse part, not the args. This can lead to out of bounds writes. The bug only gets detected if DPDK is compiled with LTO. In function ‘test_argparse_copy’, inlined from ‘test_a