From: Maurizio Lombardi <mlombard@redhat.com>
To: Mike Christie <michael.christie@oracle.com>
Cc: target-devel@vger.kernel.org, martin.petersen@oracle.com,
linux-scsi@vger.kernel.org,
james.bottomley@hansenpartnership.com,
kernel test robot <lkp@intel.com>
Subject: Re: [PATCH 1/1] target: Use RCU helpers for INQUIRY t10_alua_tg_pt_gp use
Date: Thu, 18 Nov 2021 18:14:19 +0100 [thread overview]
Message-ID: <20211118171419.GC144997@raketa> (raw)
In-Reply-To: <20211117213928.8634-1-michael.christie@oracle.com>
On Wed, Nov 17, 2021 at 03:39:28PM -0600, Mike Christie wrote:
> This fixes the sparse warnings about t10_alua_tg_pt_gp accesses in
> target_core_spc.c from:
>
> commit 7324f47d4293 ("scsi: target: Replace lun_tg_pt_gp_lock with rcu in
> I/O path")
>
> That patch replaced the lun_tg_pt_gp_lock use in the IO path, but didn't
> update the INQUIRY code.
>
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Mike Christie <michael.christie@oracle.com>
> ---
> drivers/target/target_core_spc.c | 14 +++++++-------
> 1 file changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/target/target_core_spc.c b/drivers/target/target_core_spc.c
> index 22703a0dbd07..4c76498d3fb0 100644
> --- a/drivers/target/target_core_spc.c
> +++ b/drivers/target/target_core_spc.c
> @@ -40,11 +40,11 @@ static void spc_fill_alua_data(struct se_lun *lun, unsigned char *buf)
> *
> * See spc4r17 section 6.4.2 Table 135
> */
> - spin_lock(&lun->lun_tg_pt_gp_lock);
> - tg_pt_gp = lun->lun_tg_pt_gp;
> + rcu_read_lock();
> + tg_pt_gp = rcu_dereference(lun->lun_tg_pt_gp);
> if (tg_pt_gp)
> buf[5] |= tg_pt_gp->tg_pt_gp_alua_access_type;
> - spin_unlock(&lun->lun_tg_pt_gp_lock);
> + rcu_read_unlock();
> }
>
> static u16
> @@ -325,14 +325,14 @@ spc_emulate_evpd_83(struct se_cmd *cmd, unsigned char *buf)
> * Get the PROTOCOL IDENTIFIER as defined by spc4r17
> * section 7.5.1 Table 362
> */
> - spin_lock(&lun->lun_tg_pt_gp_lock);
> - tg_pt_gp = lun->lun_tg_pt_gp;
> + rcu_read_lock();
> + tg_pt_gp = rcu_dereference(lun->lun_tg_pt_gp);
> if (!tg_pt_gp) {
> - spin_unlock(&lun->lun_tg_pt_gp_lock);
> + rcu_read_unlock();
> goto check_lu_gp;
> }
> tg_pt_gp_id = tg_pt_gp->tg_pt_gp_id;
> - spin_unlock(&lun->lun_tg_pt_gp_lock);
> + rcu_read_unlock();
>
> buf[off] = tpg->proto_id << 4;
> buf[off++] |= 0x1; /* CODE SET == Binary */
> --
> 2.25.1
>
Looks ok,
Reviewed-by: Maurizio Lombardi <mlombard@redhat.com>
next prev parent reply other threads:[~2021-11-18 17:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 21:39 [PATCH 1/1] target: Use RCU helpers for INQUIRY t10_alua_tg_pt_gp use Mike Christie
2021-11-18 17:14 ` Maurizio Lombardi [this message]
2021-11-19 4:16 ` Martin K. Petersen
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=20211118171419.GC144997@raketa \
--to=mlombard@redhat.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=martin.petersen@oracle.com \
--cc=michael.christie@oracle.com \
--cc=target-devel@vger.kernel.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