From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Bean Huo'" <beanhuo@iokpp.de>, <avri.altman@wdc.com>,
<jejb@linux.ibm.com>, <martin.petersen@oracle.com>,
<beanhuo@micron.com>, <bvanassche@acm.org>,
<quic_cang@quicinc.com>, <quic_xiaosenh@quicinc.com>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
"'kernel test robot'" <lkp@intel.com>
Subject: RE: [PATCH ] scsi: ufs: core: bsg: Fix sometimes-uninitialized warnings
Date: Mon, 2 Jan 2023 10:28:30 +0530 [thread overview]
Message-ID: <01ac01d91e66$e18d6da0$a4a848e0$@samsung.com> (raw)
In-Reply-To: <20221231150343.146274-1-beanhuo@iokpp.de>
Hi Bean,
>-----Original Message-----
>From: Bean Huo [mailto:beanhuo@iokpp.de]
>Sent: Saturday, December 31, 2022 8:34 PM
>To: alim.akhtar@samsung.com; avri.altman@wdc.com; jejb@linux.ibm.com;
>martin.petersen@oracle.com; beanhuo@micron.com; bvanassche@acm.org;
>quic_cang@quicinc.com; quic_xiaosenh@quicinc.com
>Cc: linux-scsi@vger.kernel.org; linux-kernel@vger.kernel.org; kernel test
>robot <lkp@intel.com>
>Subject: [PATCH ] scsi: ufs: core: bsg: Fix sometimes-uninitialized
warnings
>
>From: Bean Huo <beanhuo@micron.com>
>
>Compilation complains that two possible variables are used without
>initialization:
>
>drivers/ufs/core/ufs_bsg.c:112:6: warning: variable 'sg_cnt' is used
>uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
>drivers/ufs/core/ufs_bsg.c:112:6: warning: variable 'sg_list' is used
>uninitialized whenever 'if' condition is false [-Wsometimes-uninitialized]
>
>Fix both warnings by adding initialization with sg_cnt = 0, sg_list = NULL.
>
>Fixes: 6ff265fc5ef6 ("scsi: ufs: core: bsg: Add advanced RPMB support in
>ufs_bsg")
>Signed-off-by: Bean Huo <beanhuo@micron.com>
>Reported-by: kernel test robot <lkp@intel.com>
>Reported-by: Xiaosen He <quic_xiaosenh@quicinc.com>
>---
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
>Hi Martin,
>
>This patch is to fix two compilation warnings introduced by my commit:
>6ff265fc5ef6 ("scsi: ufs: core: bsg: Add advanced RPMB support in
ufs_bsg").
>
>Apologies for this.
>
>---
> drivers/ufs/core/ufs_bsg.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/ufs/core/ufs_bsg.c b/drivers/ufs/core/ufs_bsg.c index
>0044029bcf7b..0d38e7fa34cc 100644
>--- a/drivers/ufs/core/ufs_bsg.c
>+++ b/drivers/ufs/core/ufs_bsg.c
>@@ -70,9 +70,9 @@ static int ufs_bsg_exec_advanced_rpmb_req(struct
>ufs_hba *hba, struct bsg_job *j
> struct ufs_rpmb_reply *rpmb_reply = job->reply;
> struct bsg_buffer *payload = NULL;
> enum dma_data_direction dir;
>- struct scatterlist *sg_list;
>+ struct scatterlist *sg_list = NULL;
> int rpmb_req_type;
>- int sg_cnt;
>+ int sg_cnt = 0;
> int ret;
> int data_len;
>
>--
>2.25.1
prev parent reply other threads:[~2023-01-02 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221231150441epcas5p376dfc9832b2a0e1dc6ea9f98b80a2ecb@epcas5p3.samsung.com>
2022-12-31 15:03 ` [PATCH ] scsi: ufs: core: bsg: Fix sometimes-uninitialized warnings Bean Huo
2023-01-02 4:58 ` Alim Akhtar [this message]
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='01ac01d91e66$e18d6da0$a4a848e0$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=beanhuo@iokpp.de \
--cc=beanhuo@micron.com \
--cc=bvanassche@acm.org \
--cc=jejb@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=quic_cang@quicinc.com \
--cc=quic_xiaosenh@quicinc.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