[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e48d6cc9-9bb2-47fc-ec04-eceecbe6d91e@mellanox.com>
Date: Tue, 19 Mar 2019 13:41:49 +0000
From: Boris Pismenny <borisp@...lanox.com>
To: Aditya Pakki <pakki001@....edu>
CC: "kjlu@....edu" <kjlu@....edu>,
Saeed Mahameed <saeedm@...lanox.com>,
Leon Romanovsky <leon@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Ilya Lesokhin <ilyal@...lanox.com>,
Wei Yongjun <weiyongjun1@...wei.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-rdma@...r.kernel.org" <linux-rdma@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] net: mlx5: Add a missing check on idr_find
On 3/19/2019 12:18 AM, Aditya Pakki wrote:
> idr_find() can return a NULL value to 'flow' which is used without a check.
> The patch adds a check to avoid potential NULL pointer dereference.
Did you encounter this in practice?
This flow you are suggesting shouldn't be possible, because the handle
is always there until the socket is destroyed in sk_destruct.
But, I wouldn't mind some defensive coding here.
Maybe also a WARN_ONCE :)
Could you also release buf in case of an error returned from
mlx5_fpga_sbu_conn_sendmsg below?
Otherwise, I could submit a patch for this.
Powered by blists - more mailing lists