From: Dan Carpenter <error27@gmail.com>
To: oe-kbuild@lists.linux.dev,
Priyank Rathod <rathodpriyank@google.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Shuah Khan <skhan@linuxfoundation.org>,
Kees Cook <kees@kernel.org>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
Jonathan Corbet <corbet@lwn.net>
Cc: lkp@intel.com, oe-kbuild-all@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kselftest@vger.kernel.org, linux-hardening@vger.kernel.org,
linux-doc@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: Re: [PATCH v6] PCI/pcie: Add PCIe Lane Margining at Receiver (LMR) support
Date: Wed, 9 Sep 2026 13:38:51 +0300 [thread overview]
Message-ID: <202608260405.gHL6gOJf-lkp@intel.com> (raw)
In-Reply-To: <20260824-pcie-lmt-v6-1-bab4ce233fa5@google.com>
Hi Priyank,
kernel test robot noticed the following build warnings:
url: https://github.com/intel-lab-lkp/linux/commits/Priyank-Rathod/PCI-pcie-Add-PCIe-Lane-Margining-at-Receiver-LMR-support/20260824-223812
base: 0f23d56f17fdfc7db69d51f64c8b91bbab947aa9
patch link: https://lore.kernel.org/r/20260824-pcie-lmt-v6-1-bab4ce233fa5%40google.com
patch subject: [PATCH v6] PCI/pcie: Add PCIe Lane Margining at Receiver (LMR) support
config: powerpc64-randconfig-r073-20260826 (https://download.01.org/0day-ci/archive/20260826/202608260405.gHL6gOJf-lkp@intel.com/config)
compiler: powerpc64-linux-gcc (GCC) 15.2.0
smatch: v0.5.0-9187-g5189e3fb
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Reported-by: Dan Carpenter <error27@gmail.com>
| Closes: https://lore.kernel.org/r/202608260405.gHL6gOJf-lkp@intel.com/
smatch warnings:
drivers/pci/pcie/margin.c:1005 pci_lmr_exit() warn: variable dereferenced before check 'dev' (see line 1003)
drivers/pci/pcie/margin.c:1020 pci_suspend_lmr() warn: variable dereferenced before check 'dev' (see line 1018)
drivers/pci/pcie/margin.c:1056 pci_reset_lmr() warn: variable dereferenced before check 'dev' (see line 1054)
vim +/dev +1005 drivers/pci/pcie/margin.c
ecb76f560cf217 Priyank Rathod 2026-08-24 1001 void pci_lmr_exit(struct pci_dev *dev)
ecb76f560cf217 Priyank Rathod 2026-08-24 1002 {
ecb76f560cf217 Priyank Rathod 2026-08-24 @1003 struct pci_margin_dev *mdev = dev->lmr;
^^^^^
Dereference
ecb76f560cf217 Priyank Rathod 2026-08-24 1004
ecb76f560cf217 Priyank Rathod 2026-08-24 @1005 if (!dev || !mdev)
^^^^
This check is too late. It can likely be removed. The other warnings
are the same.
ecb76f560cf217 Priyank Rathod 2026-08-24 1006 return;
ecb76f560cf217 Priyank Rathod 2026-08-24 1007
ecb76f560cf217 Priyank Rathod 2026-08-24 1008 pci_suspend_lmr(dev);
ecb76f560cf217 Priyank Rathod 2026-08-24 1009
ecb76f560cf217 Priyank Rathod 2026-08-24 1010 pci_margin_debugfs_remove(mdev);
ecb76f560cf217 Priyank Rathod 2026-08-24 1011 mutex_destroy(&mdev->lock);
ecb76f560cf217 Priyank Rathod 2026-08-24 1012 kfree(mdev);
ecb76f560cf217 Priyank Rathod 2026-08-24 1013 dev->lmr = NULL;
ecb76f560cf217 Priyank Rathod 2026-08-24 1014 }
ecb76f560cf217 Priyank Rathod 2026-08-24 1015
ecb76f560cf217 Priyank Rathod 2026-08-24 1016 void pci_suspend_lmr(struct pci_dev *dev)
ecb76f560cf217 Priyank Rathod 2026-08-24 1017 {
ecb76f560cf217 Priyank Rathod 2026-08-24 @1018 struct pci_margin_dev *mdev = dev->lmr;
ecb76f560cf217 Priyank Rathod 2026-08-24 1019
ecb76f560cf217 Priyank Rathod 2026-08-24 @1020 if (!dev || !mdev)
ecb76f560cf217 Priyank Rathod 2026-08-24 1021 return;
ecb76f560cf217 Priyank Rathod 2026-08-24 1022
ecb76f560cf217 Priyank Rathod 2026-08-24 1023 guard(mutex)(&mdev->lock);
ecb76f560cf217 Priyank Rathod 2026-08-24 1024 pci_lmr_disable_locked(mdev);
ecb76f560cf217 Priyank Rathod 2026-08-24 1025 }
ecb76f560cf217 Priyank Rathod 2026-08-24 1026
ecb76f560cf217 Priyank Rathod 2026-08-24 1027 static void pci_lmr_reset_software_state_locked(struct pci_margin_dev *mdev)
ecb76f560cf217 Priyank Rathod 2026-08-24 1028 {
ecb76f560cf217 Priyank Rathod 2026-08-24 1029 struct pci_dev *dev;
ecb76f560cf217 Priyank Rathod 2026-08-24 1030 int i;
ecb76f560cf217 Priyank Rathod 2026-08-24 1031
ecb76f560cf217 Priyank Rathod 2026-08-24 1032 if (!mdev)
ecb76f560cf217 Priyank Rathod 2026-08-24 1033 return;
ecb76f560cf217 Priyank Rathod 2026-08-24 1034
ecb76f560cf217 Priyank Rathod 2026-08-24 1035 lockdep_assert_held(&mdev->lock);
ecb76f560cf217 Priyank Rathod 2026-08-24 1036
ecb76f560cf217 Priyank Rathod 2026-08-24 1037 if (!mdev->enabled)
ecb76f560cf217 Priyank Rathod 2026-08-24 1038 return;
ecb76f560cf217 Priyank Rathod 2026-08-24 1039
ecb76f560cf217 Priyank Rathod 2026-08-24 1040 dev = mdev->dev;
ecb76f560cf217 Priyank Rathod 2026-08-24 1041
ecb76f560cf217 Priyank Rathod 2026-08-24 1042 for (i = 0; i < mdev->num_lanes; i++) {
ecb76f560cf217 Priyank Rathod 2026-08-24 1043 mdev->lanes[i].timing_val = 0;
ecb76f560cf217 Priyank Rathod 2026-08-24 1044 mdev->lanes[i].voltage_val = 0;
ecb76f560cf217 Priyank Rathod 2026-08-24 1045 }
ecb76f560cf217 Priyank Rathod 2026-08-24 1046
ecb76f560cf217 Priyank Rathod 2026-08-24 1047 pci_lmr_restore_aspm(mdev);
ecb76f560cf217 Priyank Rathod 2026-08-24 1048 pm_runtime_put_sync(&dev->dev);
ecb76f560cf217 Priyank Rathod 2026-08-24 1049 mdev->enabled = false;
ecb76f560cf217 Priyank Rathod 2026-08-24 1050 }
ecb76f560cf217 Priyank Rathod 2026-08-24 1051
ecb76f560cf217 Priyank Rathod 2026-08-24 1052 void pci_reset_lmr(struct pci_dev *dev)
ecb76f560cf217 Priyank Rathod 2026-08-24 1053 {
ecb76f560cf217 Priyank Rathod 2026-08-24 @1054 struct pci_margin_dev *mdev = dev->lmr;
ecb76f560cf217 Priyank Rathod 2026-08-24 1055
ecb76f560cf217 Priyank Rathod 2026-08-24 @1056 if (!dev || !mdev)
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2026-09-09 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-24 22:38 Priyank Rathod
2026-08-25 11:02 ` Ilpo Järvinen
2026-09-09 10:38 ` Dan Carpenter [this message]
2026-09-09 17:37 ` Priyank Rathod
-- strict thread matches above, loose matches on Subject: below --
2026-08-24 22:37 Priyank Rathod
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=202608260405.gHL6gOJf-lkp@intel.com \
--to=error27@gmail.com \
--cc=corbet@lwn.net \
--cc=gustavoars@kernel.org \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kees@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=oe-kbuild@lists.linux.dev \
--cc=rathodpriyank@google.com \
--cc=skhan@linuxfoundation.org \
/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®