mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Julia Lawall <julia.lawall@inria.fr>
To: Vadim Pasternak <vadimp@nvidia.com>
Cc: Jiri Pirko <jiri@nvidia.com>,
	kbuild-all@lists.01.org, linux-kernel@vger.kernel.org
Subject: [jpirko-mlxsw:linecards 110/112] drivers/platform/mellanox/mlxreg-lc.c:485:1-7: preceding lock on line 469 (fwd)
Date: Sat, 28 Aug 2021 13:07:15 +0200 (CEST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2108281306110.10588@hadrien> (raw)

[-- Attachment #1: Type: text/plain, Size: 3038 bytes --]

This looks suspicious.  Maybe the fail label shoudl be before line 482 to
include the unlock?

julia

---------- Forwarded message ----------
Date: Thu, 26 Aug 2021 05:55:03 +0800
From: kernel test robot <lkp@intel.com>
To: kbuild@lists.01.org
Cc: lkp@intel.com, Julia Lawall <julia.lawall@lip6.fr>
Subject: [jpirko-mlxsw:linecards 110/112]
    drivers/platform/mellanox/mlxreg-lc.c:485:1-7: preceding lock on line 469

CC: kbuild-all@lists.01.org
CC: linux-kernel@vger.kernel.org
TO: Vadim Pasternak <vadimp@nvidia.com>
CC: Jiri Pirko <jiri@nvidia.com>

tree:   https://github.com/jpirko/linux_mlxsw linecards
head:   a37df1af1f3e6a47a9718298d5e50b842f79b2d2
commit: fbdba1b20b39b5e3b79d6df5b44cc5be3a0ddc0c [110/112] TMP: platform/mellanox
:::::: branch date: 9 hours ago
:::::: commit date: 12 hours ago
config: xtensa-randconfig-c023-20210825 (attached as .config)
compiler: xtensa-linux-gcc (GCC) 11.2.0

If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
Reported-by: Julia Lawall <julia.lawall@lip6.fr>


cocci warnings: (new ones prefixed by >>)
>> drivers/platform/mellanox/mlxreg-lc.c:485:1-7: preceding lock on line 469

vim +485 drivers/platform/mellanox/mlxreg-lc.c

b386a25dac45ae Vadim Pasternak 2021-03-25  463
b386a25dac45ae Vadim Pasternak 2021-03-25  464  static int mlxreg_lc_power_on_off(struct mlxreg_lc *mlxreg_lc, u8 action)
b386a25dac45ae Vadim Pasternak 2021-03-25  465  {
b386a25dac45ae Vadim Pasternak 2021-03-25  466  	u32 regval;
b386a25dac45ae Vadim Pasternak 2021-03-25  467  	int err;
b386a25dac45ae Vadim Pasternak 2021-03-25  468
fbdba1b20b39b5 Vadim Pasternak 2021-07-01 @469  	mutex_lock(&mlxreg_lc->lock);
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  470
b386a25dac45ae Vadim Pasternak 2021-03-25  471  	err = regmap_read(mlxreg_lc->par_regmap, mlxreg_lc->data->reg_pwr, &regval);
b386a25dac45ae Vadim Pasternak 2021-03-25  472  	if (err)
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  473  		goto regmap_read_fail;
b386a25dac45ae Vadim Pasternak 2021-03-25  474
b386a25dac45ae Vadim Pasternak 2021-03-25  475  	if (action)
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  476  		regval |= BIT(mlxreg_lc->data->slot - 1);
b386a25dac45ae Vadim Pasternak 2021-03-25  477  	else
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  478  		regval &= ~BIT(mlxreg_lc->data->slot - 1);
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  479
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  480  	err = regmap_write(mlxreg_lc->par_regmap, mlxreg_lc->data->reg_pwr, regval);
b386a25dac45ae Vadim Pasternak 2021-03-25  481
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  482  	mutex_unlock(&mlxreg_lc->lock);
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  483
fbdba1b20b39b5 Vadim Pasternak 2021-07-01  484  regmap_read_fail:
fbdba1b20b39b5 Vadim Pasternak 2021-07-01 @485  	return err;
b386a25dac45ae Vadim Pasternak 2021-03-25  486  }
b386a25dac45ae Vadim Pasternak 2021-03-25  487

---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org

[-- Attachment #2: Type: application/gzip, Size: 32878 bytes --]

                 reply	other threads:[~2021-08-28 11:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2108281306110.10588@hadrien \
    --to=julia.lawall@inria.fr \
    --cc=jiri@nvidia.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vadimp@nvidia.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®