From: kernel test robot <lkp@intel.com>
To: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
linux-kernel@vger.kernel.org, iommu@lists.linux.dev
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
joro@8bytes.org, robin.murphy@arm.com, vasant.hegde@amd.com,
ubizjak@gmail.com, jgg@nvidia.com, jon.grimm@amd.com,
santosh.shukla@amd.com, pandoh@google.com, kumaranand@google.com,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH v3 2/5] iommu/amd: Introduce helper functions to access and update 256-bit DTE
Date: Sat, 7 Sep 2024 21:36:46 +0800 [thread overview]
Message-ID: <202409072100.WaB846Yg-lkp@intel.com> (raw)
In-Reply-To: <20240906121308.5013-3-suravee.suthikulpanit@amd.com>
Hi Suravee,
kernel test robot noticed the following build warnings:
[auto build test WARNING on linus/master]
[also build test WARNING on joro-iommu/next v6.11-rc6 next-20240906]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Suravee-Suthikulpanit/iommu-amd-Disable-AMD-IOMMU-if-CMPXCHG16B-feature-is-not-supported/20240906-201533
base: linus/master
patch link: https://lore.kernel.org/r/20240906121308.5013-3-suravee.suthikulpanit%40amd.com
patch subject: [PATCH v3 2/5] iommu/amd: Introduce helper functions to access and update 256-bit DTE
config: x86_64-rhel-8.3-rust (https://download.01.org/0day-ci/archive/20240907/202409072100.WaB846Yg-lkp@intel.com/config)
compiler: clang version 18.1.5 (https://github.com/llvm/llvm-project 617a15a9eac96088ae5e9134248d8236e34b91b1)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240907/202409072100.WaB846Yg-lkp@intel.com/reproduce)
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>
| Closes: https://lore.kernel.org/oe-kbuild-all/202409072100.WaB846Yg-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/iommu/amd/iommu.c:299:6: warning: variable 'ret' is used uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
299 | if (!alias_data) {
| ^~~~~~~~~~~
drivers/iommu/amd/iommu.c:309:9: note: uninitialized use occurs here
309 | return ret;
| ^~~
drivers/iommu/amd/iommu.c:299:2: note: remove the 'if' if its condition is always true
299 | if (!alias_data) {
| ^~~~~~~~~~~~~~~~
drivers/iommu/amd/iommu.c:279:9: note: initialize the variable 'ret' to silence this warning
279 | int ret;
| ^
| = 0
1 warning generated.
vim +299 drivers/iommu/amd/iommu.c
272
273 static int clone_alias(struct pci_dev *pdev, u16 alias, void *data)
274 {
275 struct dev_table_entry dte;
276 struct amd_iommu *iommu;
277 struct iommu_dev_data *dev_data, *alias_data;
278 u16 devid = pci_dev_id(pdev);
279 int ret;
280
281 if (devid == alias)
282 return 0;
283
284 iommu = rlookup_amd_iommu(&pdev->dev);
285 if (!iommu)
286 return 0;
287
288 /* Get DTE for pdev */
289 dev_data = dev_iommu_priv_get(&pdev->dev);
290 if (!dev_data)
291 return -EINVAL;
292
293 spin_lock(&dev_data->dte_lock);
294 get_dte256(iommu, dev_data, &dte);
295 spin_unlock(&dev_data->dte_lock);
296
297 /* Setup for alias */
298 alias_data = search_dev_data(iommu, alias);
> 299 if (!alias_data) {
300 ret = -EINVAL;
301 goto out;
302 }
303
304 spin_lock(&alias_data->dte_lock);
305 update_dte256(iommu, alias_data, &dte);
306 amd_iommu_set_rlookup_table(iommu, alias);
307 spin_unlock(&alias_data->dte_lock);
308 out:
309 return ret;
310 }
311
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-09-07 13:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 12:13 [PATCH v3 0/5] iommu/amd: Use 128-bit cmpxchg operation to update DTE Suravee Suthikulpanit
2024-09-06 12:13 ` [PATCH v3 1/5] iommu/amd: Disable AMD IOMMU if CMPXCHG16B feature is not supported Suravee Suthikulpanit
2024-09-06 16:38 ` Jason Gunthorpe
2024-09-09 15:16 ` Jason Gunthorpe
2024-09-16 17:19 ` Suthikulpanit, Suravee
2024-09-16 16:11 ` Suthikulpanit, Suravee
2024-09-23 18:13 ` Jason Gunthorpe
2024-09-06 12:13 ` [PATCH v3 2/5] iommu/amd: Introduce helper functions to access and update 256-bit DTE Suravee Suthikulpanit
2024-09-06 15:53 ` Jacob Pan
2024-09-06 17:00 ` Jason Gunthorpe
2024-09-16 16:12 ` Suthikulpanit, Suravee
[not found] ` <66db2589.170a0220.6f57.d691SMTPIN_ADDED_BROKEN@mx.google.com>
2024-09-06 19:31 ` Uros Bizjak
2024-09-07 13:36 ` kernel test robot [this message]
2024-09-06 12:13 ` [PATCH v3 3/5] iommu/amd: Modify set_dte_entry() to use 256-bit DTE helpers Suravee Suthikulpanit
2024-09-06 12:13 ` [PATCH v3 4/5] iommu/amd: Modify clear_dte_entry() to avoid in-place update Suravee Suthikulpanit
2024-09-06 18:07 ` Jason Gunthorpe
2024-09-06 12:13 ` [PATCH v3 5/5] iommu/amd: Do not update DTE in-place in amd_iommu_set_dirty_tracking and set_dte_irq_entry Suravee Suthikulpanit
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=202409072100.WaB846Yg-lkp@intel.com \
--to=lkp@intel.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=joro@8bytes.org \
--cc=kumaranand@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pandoh@google.com \
--cc=robin.murphy@arm.com \
--cc=santosh.shukla@amd.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=ubizjak@gmail.com \
--cc=vasant.hegde@amd.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®