From: kernel test robot <lkp@intel.com>
To: oe-kbuild@lists.linux.dev
Cc: lkp@intel.com, Dan Carpenter <error27@gmail.com>
Subject: [android-common:android14-5.15-lts 29/29] drivers/ufs/core/ufs-mcq.c:293 ufshcd_mcq_poll_cqe_nolock() error: we previously assumed 'compl_cmd' could be null (see line 292)
Date: Thu, 19 Nov 2026 08:41:43 +0100 [thread overview]
Message-ID: <20261119083916.lKKo8kHM-lkp@intel.com> (raw)
Unfiltered warning: this smatch report is sent as-is and has not been
reviewed for false positives, so please treat it with due skepticism.
BCC: lkp@intel.com
CC: oe-kbuild-all@lists.linux.dev
TO: cros-kernel-buildreports@googlegroups.com
tree: https://android.googlesource.com/kernel/common android14-5.15-lts
head: 6a30f9e067712464f3f2299dc278bcb5be365a3e
commit: 8563ce58954679187f0c269a504520d8def37e41 [29/29] BACKPORT: FROMLIST: scsi: ufs: Make the polling code report which command has been completed
:::::: branch date: 2 days ago
:::::: commit date: 2 years, 7 months ago
config: i386-randconfig-2200-20261118 (https://download.01.org/0day-ci/archive/20261119/20261119083916.lKKo8kHM-lkp@intel.com/config)
compiler: gcc-13 (Debian 13.3.0-16) 13.3.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/20261119083916.lKKo8kHM-lkp@intel.com/
smatch warnings:
drivers/ufs/core/ufs-mcq.c:293 ufshcd_mcq_poll_cqe_nolock() error: we previously assumed 'compl_cmd' could be null (see line 292)
vim +/compl_cmd +293 drivers/ufs/core/ufs-mcq.c
31fe4a16211a23 Asutosh Das 2023-01-13 281
8563ce58954679 Bart Van Assche 2024-04-11 282 /* Clears *@compl_cmd if and only if *@compl_cmd has been completed. */
31fe4a16211a23 Asutosh Das 2023-01-13 283 unsigned long ufshcd_mcq_poll_cqe_nolock(struct ufs_hba *hba,
8563ce58954679 Bart Van Assche 2024-04-11 284 struct ufs_hw_queue *hwq,
8563ce58954679 Bart Van Assche 2024-04-11 285 struct scsi_cmnd **compl_cmd)
31fe4a16211a23 Asutosh Das 2023-01-13 286 {
31fe4a16211a23 Asutosh Das 2023-01-13 287 unsigned long completed_reqs = 0;
31fe4a16211a23 Asutosh Das 2023-01-13 288
31fe4a16211a23 Asutosh Das 2023-01-13 289 ufshcd_mcq_update_cq_tail_slot(hwq);
31fe4a16211a23 Asutosh Das 2023-01-13 290 while (!ufshcd_mcq_is_cq_empty(hwq)) {
8563ce58954679 Bart Van Assche 2024-04-11 291 if (ufshcd_mcq_process_cqe(hba, hwq,
8563ce58954679 Bart Van Assche 2024-04-11 @292 compl_cmd ? *compl_cmd : NULL))
8563ce58954679 Bart Van Assche 2024-04-11 @293 *compl_cmd = NULL;
31fe4a16211a23 Asutosh Das 2023-01-13 294 ufshcd_mcq_inc_cq_head_slot(hwq);
31fe4a16211a23 Asutosh Das 2023-01-13 295 completed_reqs++;
31fe4a16211a23 Asutosh Das 2023-01-13 296 }
31fe4a16211a23 Asutosh Das 2023-01-13 297
31fe4a16211a23 Asutosh Das 2023-01-13 298 if (completed_reqs)
31fe4a16211a23 Asutosh Das 2023-01-13 299 ufshcd_mcq_update_cq_head(hwq);
31fe4a16211a23 Asutosh Das 2023-01-13 300
31fe4a16211a23 Asutosh Das 2023-01-13 301 return completed_reqs;
31fe4a16211a23 Asutosh Das 2023-01-13 302 }
31fe4a16211a23 Asutosh Das 2023-01-13 303
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-11-19 7:42 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=20261119083916.lKKo8kHM-lkp@intel.com \
--to=lkp@intel.com \
--cc=error27@gmail.com \
--cc=oe-kbuild@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.