Re: [PATCH] event/octeontx: resolve possible integer overflow

2024-10-18 Thread Stephen Hemminger
On Fri, 18 Oct 2024 13:29:03 +0530 Hanumanth Pothula wrote: > The last argument passed to ssovf_parsekv() is an > unsigned char*, but it is accessed as an integer. > This can lead to an integer overflow. > > Hence, make ensure the argument is accessed as a char > and for better error handling us

RE: [EXTERNAL] [PATCH] event/octeontx: resolve possible integer overflow

2024-10-18 Thread Pavan Nikhilesh Bhagavatula
> The last argument passed to ssovf_parsekv() is an > unsigned char*, but it is accessed as an integer. > This can lead to an integer overflow. > > Hence, make ensure the argument is accessed as a char > and for better error handling use strtol instead of atoi. > > Signed-off-by: Hanumanth Pothul

[PATCH] event/octeontx: resolve possible integer overflow

2024-10-18 Thread Hanumanth Pothula
The last argument passed to ssovf_parsekv() is an unsigned char*, but it is accessed as an integer. This can lead to an integer overflow. Hence, make ensure the argument is accessed as a char and for better error handling use strtol instead of atoi. Signed-off-by: Hanumanth Pothula --- drivers/