Re: [net-next 03/14] net/mlx5e: rep, store send to vport rules per peer

[Saeed Mahameed <saeed@kernel.org>]

On 02 Jun 18:02, Simon Horman wrote:
>On Wed, May 31, 2023 at 11:01:07PM -0700, Saeed Mahameed wrote:
>> From: Mark Bloch <mbloch@nvidia.com>
>>
>> Each representor, for each send queue, is holding a
>> send_to_vport rule for the peer eswitch.
>>
>> In order to support more than one peer, and to map between the peer
>> rules and peer eswitches, refactor representor to hold both the peer
>> rules and pointer to the peer eswitches.
>> This enables mlx5 to store send_to_vport rules per peer, where each
>> peer have dedicate index via mlx5_get_dev_index().
>>
>> Signed-off-by: Mark Bloch <mbloch@nvidia.com>
>> Signed-off-by: Shay Drory <shayd@nvidia.com>
>> Reviewed-by: Roi Dayan <roid@nvidia.com>
>> Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
>
>...
>
>> @@ -426,15 +437,24 @@ static int mlx5e_sqs2vport_start(struct mlx5_eswitch *esw,
>>  		rep_sq->sqn = sqns_array[i];
>>
>>  		if (peer_esw) {
>> +			int peer_rule_idx = mlx5_get_dev_index(peer_esw->dev);
>> +
>> +			sq_peer = kzalloc(sizeof(*sq_peer), GFP_KERNEL);
>> +			if (!sq_peer)
>> +				goto out_sq_peer_err;
>
>Hi Mark and Saeed,
>
>Jumping to out_sq_peer_err will return err.
>But err seems to be uninitialised here.
>

Thanks Simon, They change this logic in a later refactoring patch:
"net/mlx5: Devcom, introduce devcom_for_each_peer_entry" 
where this issue doesn't exist anymore, but i will fix anyway..

Thanks,
Saeed.