[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DM8PR11MB5621D36AB45F5BA962527766AB389@DM8PR11MB5621.namprd11.prod.outlook.com>
Date: Thu, 3 Nov 2022 11:46:31 +0000
From: "Jankowski, Konrad0" <konrad0.jankowski@...el.com>
To: Stefan Assmann <sassmann@...nic.de>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
CC: "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Piotrowski, Patryk" <patryk.piotrowski@...el.com>
Subject: RE: [Intel-wired-lan] [PATCH net-next] iavf: check that state
transitions happen under lock
> -----Original Message-----
> From: Intel-wired-lan <intel-wired-lan-bounces@...osl.org> On Behalf Of Stefan
> Assmann
> Sent: Friday, October 28, 2022 3:45 PM
> To: intel-wired-lan@...ts.osuosl.org
> Cc: netdev@...r.kernel.org; Piotrowski, Patryk <patryk.piotrowski@...el.com>;
> sassmann@...nic.de
> Subject: [Intel-wired-lan] [PATCH net-next] iavf: check that state transitions
> happen under lock
>
> Add a check to make sure crit_lock is being held during every state transition and
> print a warning if that's not the case. For convenience a wrapper is added that
> helps pointing out where the locking is missing.
>
> Make an exception for iavf_probe() as that is too early in the init process and
> generates a false positive report.
>
> Signed-off-by: Stefan Assmann <sassmann@...nic.de>
> ---
> drivers/net/ethernet/intel/iavf/iavf.h | 23 +++++++++++++++------
> drivers/net/ethernet/intel/iavf/iavf_main.c | 2 +-
> 2 files changed, 18 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/net/ethernet/intel/iavf/iavf.h
> b/drivers/net/ethernet/intel/iavf/iavf.h
> index 3f6187c16424..28f41bbc9c86 100644
> --- a/drivers/net/ethernet/intel/iavf/iavf.h
> +++ b/drivers/net/ethernet/intel/iavf/iavf.h
Tested-by: Konrad Jankowski <konrad0.jankowski@...el.com>
Powered by blists - more mailing lists