[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4183c48a-3c78-47e2-a7b2-11d387b6f833@nvidia.com>
Date: Tue, 3 Dec 2024 11:44:12 +0200
From: Yevgeny Kliteynik <kliteyn@...dia.com>
To: Dan Carpenter <dan.carpenter@...aro.org>,
Mateusz Polchlopek <mateusz.polchlopek@...el.com>
Cc: Saeed Mahameed <saeedm@...dia.com>, Leon Romanovsky <leon@...nel.org>,
Tariq Toukan <tariqt@...dia.com>, Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
Muhammad Sammar <muhammads@...dia.com>, netdev@...r.kernel.org,
linux-rdma@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-janitors@...r.kernel.org
Subject: Re: [PATCH net] net/mlx5: DR, prevent potential error pointer
dereference
On 03-Dec-24 11:39, Dan Carpenter wrote:
> On Tue, Dec 03, 2024 at 10:32:13AM +0100, Mateusz Polchlopek wrote:
>>
>>
>> On 11/30/2024 11:01 AM, Dan Carpenter wrote:
>>> The dr_domain_add_vport_cap() function genereally returns NULL on error
>>
>> Typo. Should be "generally"
>>
>
> Sure.
>
>>> but sometimes we want it to return ERR_PTR(-EBUSY) so the caller can
>>> retry. The problem here is that "ret" can be either -EBUSY or -ENOMEM
>>
>> Please remove unnecessary space.
>>
>
> What are you talking about?
Oh, I see it :)
Double space between "retry." and "The"
-- YK
> regards,
> dan carpenter
>
>
Powered by blists - more mailing lists