Linux SCSI subsystem development
 help / color / mirror / Atom feed
From: Deepak R Varma <drv@mailo.com>
To: Hannes Reinecke <hare@suse.de>,
	"James E.J. Bottomley" <jejb@linux.ibm.com>,
	"Martin K. Petersen" <martin.petersen@oracle.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Saurabh Singh Sengar <ssengar@microsoft.com>,
	Praveen Kumar <kumarpraveen@linux.microsoft.com>,
	Deepak R Varma <drv@mailo.com>
Subject: Re: [PATCH] scsi: libfc: Use refcount_* APIs for reference count management
Date: Wed, 28 Dec 2022 15:48:01 +0530	[thread overview]
Message-ID: <Y6wX2dVlrF8t7iVk@qemulion> (raw)
In-Reply-To: <Y6E6dVcdHk2zK+/1@qemulion>

On Tue, Dec 20, 2022 at 10:00:45AM +0530, Deepak R Varma wrote:
> The atomic_t API based object reference counter management is prone to
> counter value overflows, object use-after-free issues and to return
> puzzling values. The improved refcount_t APIs are designed to address
> these known issues with atomic_t reference counter management. This
> white paper [1] has detailed reasons for moving from atomic_t to
> refcount_t APIs. Hence replace the atomic_* based implementation by its
> refcount_* based equivalent.
> The issue is identified using atomic_as_refcounter.cocci Coccinelle
> semantic patch script.
>
> 	[1] https://arxiv.org/pdf/1710.06175.pdf
>
> Signed-off-by: Deepak R Varma <drv@mailo.com>

Hello,
May I please request a review and feedback on this patch proposal?

Thank you,
./drv

> ---
> Note: The proposal is compile tested only.
>
>  drivers/scsi/libfc/fc_exch.c | 10 +++++-----
>  include/scsi/libfc.h         |  2 +-
>  2 files changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/scsi/libfc/fc_exch.c b/drivers/scsi/libfc/fc_exch.c
> index 1d91c457527f..1c49fddb65e3 100644
> --- a/drivers/scsi/libfc/fc_exch.c
> +++ b/drivers/scsi/libfc/fc_exch.c
> @@ -246,7 +246,7 @@ static const char *fc_exch_rctl_name(unsigned int op)
>   */
>  static inline void fc_exch_hold(struct fc_exch *ep)
>  {
> -	atomic_inc(&ep->ex_refcnt);
> +	refcount_inc(&ep->ex_refcnt);
>  }
>
>  /**
> @@ -312,7 +312,7 @@ static void fc_exch_release(struct fc_exch *ep)
>  {
>  	struct fc_exch_mgr *mp;
>
> -	if (atomic_dec_and_test(&ep->ex_refcnt)) {
> +	if (refcount_dec_and_test(&ep->ex_refcnt)) {
>  		mp = ep->em;
>  		if (ep->destructor)
>  			ep->destructor(&ep->seq, ep->arg);
> @@ -329,7 +329,7 @@ static inline void fc_exch_timer_cancel(struct fc_exch *ep)
>  {
>  	if (cancel_delayed_work(&ep->timeout_work)) {
>  		FC_EXCH_DBG(ep, "Exchange timer canceled\n");
> -		atomic_dec(&ep->ex_refcnt); /* drop hold for timer */
> +		refcount_dec(&ep->ex_refcnt); /* drop hold for timer */
>  	}
>  }
>
> @@ -1897,7 +1897,7 @@ static void fc_exch_reset(struct fc_exch *ep)
>  	ep->state |= FC_EX_RST_CLEANUP;
>  	fc_exch_timer_cancel(ep);
>  	if (ep->esb_stat & ESB_ST_REC_QUAL)
> -		atomic_dec(&ep->ex_refcnt);	/* drop hold for rec_qual */
> +		refcount_dec(&ep->ex_refcnt);	/* drop hold for rec_qual */
>  	ep->esb_stat &= ~ESB_ST_REC_QUAL;
>  	sp = &ep->seq;
>  	rc = fc_exch_done_locked(ep);
> @@ -2332,7 +2332,7 @@ static void fc_exch_els_rrq(struct fc_frame *fp)
>  	 */
>  	if (ep->esb_stat & ESB_ST_REC_QUAL) {
>  		ep->esb_stat &= ~ESB_ST_REC_QUAL;
> -		atomic_dec(&ep->ex_refcnt);	/* drop hold for rec qual */
> +		refcount_dec(&ep->ex_refcnt);	/* drop hold for rec qual */
>  	}
>  	if (ep->esb_stat & ESB_ST_COMPLETE)
>  		fc_exch_timer_cancel(ep);
> diff --git a/include/scsi/libfc.h b/include/scsi/libfc.h
> index 6e29e1719db1..ce65149b300c 100644
> --- a/include/scsi/libfc.h
> +++ b/include/scsi/libfc.h
> @@ -432,7 +432,7 @@ struct fc_seq {
>   */
>  struct fc_exch {
>  	spinlock_t	    ex_lock;
> -	atomic_t	    ex_refcnt;
> +	refcount_t	    ex_refcnt;
>  	enum fc_class	    class;
>  	struct fc_exch_mgr  *em;
>  	struct fc_exch_pool *pool;
> --
> 2.34.1
>



      reply	other threads:[~2022-12-28 10:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-20  4:30 [PATCH] scsi: libfc: Use refcount_* APIs for reference count management Deepak R Varma
2022-12-28 10:18 ` Deepak R Varma [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=Y6wX2dVlrF8t7iVk@qemulion \
    --to=drv@mailo.com \
    --cc=hare@suse.de \
    --cc=jejb@linux.ibm.com \
    --cc=kumarpraveen@linux.microsoft.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=ssengar@microsoft.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