Re: [PATCH][next] net/mlx5e: Fix potential null pointer dereference

2020-09-29 Thread Gustavo A. R. Silva
On Mon, Sep 28, 2020 at 04:22:33PM -0700, Saeed Mahameed wrote: > On Fri, 2020-09-25 at 11:49 -0500, Gustavo A. R. Silva wrote: > > Calls to kzalloc() and kvzalloc() should be null-checked > > in order to avoid any potential failures. In this case, > > a potential null pointer dereference. > > > >

Re: [PATCH][next] net/mlx5e: Fix potential null pointer dereference

2020-09-28 Thread Saeed Mahameed
On Fri, 2020-09-25 at 11:49 -0500, Gustavo A. R. Silva wrote: > Calls to kzalloc() and kvzalloc() should be null-checked > in order to avoid any potential failures. In this case, > a potential null pointer dereference. > > Fix this by adding null checks for _parse_attr_ and _flow_ > right after al

Re: [PATCH][next] net/mlx5e: Fix potential null pointer dereference

2020-09-28 Thread Leon Romanovsky
On Fri, Sep 25, 2020 at 11:49:13AM -0500, Gustavo A. R. Silva wrote: > Calls to kzalloc() and kvzalloc() should be null-checked > in order to avoid any potential failures. In this case, > a potential null pointer dereference. > > Fix this by adding null checks for _parse_attr_ and _flow_ > right af

[PATCH][next] net/mlx5e: Fix potential null pointer dereference

2020-09-25 Thread Gustavo A. R. Silva
Calls to kzalloc() and kvzalloc() should be null-checked in order to avoid any potential failures. In this case, a potential null pointer dereference. Fix this by adding null checks for _parse_attr_ and _flow_ right after allocation. Addresses-Coverity-ID: 1497154 ("Dereference before null check"