netdev - RE: [PATCH iwl-next v4 05/10] ice: process events created by lag netdev event handler

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <MW5PR11MB58117A92BC18CB758DF950BDDD5AA@MW5PR11MB5811.namprd11.prod.outlook.com>
Date: Wed, 14 Jun 2023 23:19:26 +0000
From: "Ertman, David M" <david.m.ertman@...el.com>
To: Brett Creeley <bcreeley@....com>, "intel-wired-lan@...ts.osuosl.org"
	<intel-wired-lan@...ts.osuosl.org>
CC: "daniel.machon@...rochip.com" <daniel.machon@...rochip.com>,
	"simon.horman@...igine.com" <simon.horman@...igine.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: [PATCH iwl-next v4 05/10] ice: process events created by lag
 netdev event handler



> -----Original Message-----
> From: Brett Creeley <bcreeley@....com>
> Sent: Wednesday, June 14, 2023 2:24 PM
> To: Ertman, David M <david.m.ertman@...el.com>; intel-wired-
> lan@...ts.osuosl.org
> Cc: daniel.machon@...rochip.com; simon.horman@...igine.com;
> netdev@...r.kernel.org
> Subject: Re: [PATCH iwl-next v4 05/10] ice: process events created by lag
> netdev event handler
> 
> On 6/9/2023 2:16 PM, Dave Ertman wrote:
> > Caution: This message originated from an External Source. Use proper
> caution when opening attachments, clicking links, or responding.
> >
> >
> > Add in the function framework for the processing of LAG events.  Also add
> > in helper function to perform common tasks.
> >
> > Add the basis of the process of linking a lower netdev to an upper netdev.
> >
> > Reviewed-by: Daniel Machon <daniel.machon@...rochip.com>
> > Signed-off-by: Dave Ertman <david.m.ertman@...el.com>
> > ---
> >   drivers/net/ethernet/intel/ice/ice_lag.c      | 535 +++++++++++++++---
> >   drivers/net/ethernet/intel/ice/ice_lag.h      |   1 +
> >   drivers/net/ethernet/intel/ice/ice_switch.c   |  10 +-
> >   drivers/net/ethernet/intel/ice/ice_switch.h   |   3 +
> >   drivers/net/ethernet/intel/ice/ice_virtchnl.c |   2 +
> >   5 files changed, 478 insertions(+), 73 deletions(-)
> >
> 
> [...]
> 
> > +/**
> > + * ice_lag_reclaim_vf_nodes - When interface leaving bond primary
> reclaims nodes
> > + * @lag: primary interface lag struct
> > + * @src_hw: HW struct for current node location
> > + */
> > +static void
> > +ice_lag_reclaim_vf_nodes(struct ice_lag *lag, struct ice_hw *src_hw)
> > +{
> > +       struct ice_pf *pf;
> > +       int i, tc;
> > +
> > +       if (!lag->primary || !src_hw)
> > +               return;
> > +
> > +       pf = lag->pf;
> > +       ice_for_each_vsi(pf, i)
> > +               if (pf->vsi[i] && (pf->vsi[i]->type == ICE_VSI_VF ||
> > +                                  pf->vsi[i]->type == ICE_VSI_SWITCHDEV_CTRL))
> > +                       ice_for_each_traffic_class(tc)
> > +                               ice_lag_reclaim_vf_tc(lag, src_hw, i, tc);
> 
> Seems like indentation got messed up here for ice_lag_reclaim_vf_tc()?
> Is this supposed to be under the if block?

Unless I am missing something, looks correct to me?  The if statement has a parenthetical
sub block that the second line of the if statement is aligning to.  The ice_for_each_traffic_class
is one indent in from the if block, and the ice_lag_reclaim_vf_tc is under the macro'd for statement.

DaveE
> 
> > +}
> > +
> 
> 
> [...]