public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <jbottomley@parallels.com>
To: Jayamohan Kallickal <jayamohank@gmail.com>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"michaelc@cs.wisc.edu" <michaelc@cs.wisc.edu>,
	Shlomo Pongratz <shlomop@mellanox.com>
Subject: Re: [PATCH V2 16/18] be2iscsi: Fix possible reentrancy issue in be_iopoll
Date: Thu, 2 May 2013 15:20:48 +0000	[thread overview]
Message-ID: <1367508048.3133.2.camel@dabdike> (raw)
In-Reply-To: <1365219519-3457-16-git-send-email-jayamohan.kallickal@emulex.com>

On Fri, 2013-04-05 at 20:38 -0700, Jayamohan Kallickal wrote:
> From: Shlomo Pongratz <shlomop@mellanox.com>
> 
>  The driver creates "NAPI" context per core which is fine,
>  however the above routine declares the ret variable as static!
>  Thus there is only one instance of this variable!
>  When this routine is called from more than one thread of execution,
>  than the result is unpredictable.
> 
>          static unsigned int ret;
>          .....
> 
>          ret = beiscsi_process_cq(pbe_eq);
>                  <--------Another thread can enter here and change "ret".
>          if (ret < budget) {
>                 ....
>          }
>                  <--------Another thread can enter here and change "ret".
>          return ret;
> 
>  Fix - remove the "static"
> 
> Signed-off-by: Shlomo Pongratz <shlomop@mellanox.com>
> Acked-by: Jayamohan Kallickal <jayamohan.kallickal@emulex.com>

The rule here is that this needs to be Signed-off-by: from you because
you sent the patch to me (signoffs follow the transmission path for the
patch).  If you just see the patch on the list and want me to apply it,
you give me an Acked-by, but if you actually pick the patch up and send
it to me it must have a signed-off-by.

I assumed your consent and changed the tag.

James


  reply	other threads:[~2013-05-02 15:20 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-06  3:38 [PATCH V2 01/18] be2iscsi: Fix lack of uninitialize pattern to FW Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 02/18] be2iscsi: Fix returning Failure when MBX fails with Insufficient buffer error Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 03/18] be2iscsi: Fix MBX Command issues Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 04/18] be2iscsi: Fix MSIX support in SKH-R to 32 Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 05/18] be2iscsi: Fix freeing CXN specific driver resources Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 06/18] be2iscsi: Fix MACRO for checking the adapter type Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 07/18] be2iscsi: Fix support for DEFQ extension Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 08/18] be2iscsi: Fix displaying the FW Version from driver Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 09/18] be2iscsi: Fix displaying the Active Session Count " Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 10/18] be2iscsi: Fix the Port Link Status issue Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 11/18] be2iscsi : Fix the NOP-In handling code path Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 12/18] be2iscsi: Fix dynamic CID allocation Mechanism in driver Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 13/18] be2iscsi: Fix checking Adapter state while establishing CXN Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 14/18] be2scsi: Fix the copyright information Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 15/18] be2iscsi: Fix the session cleanup when reboot/shutdown happens Jayamohan Kallickal
2013-04-10 23:41   ` Mike Christie
2013-04-12 20:08     ` Kallickal, Jayamohan
2013-04-06  3:38 ` [PATCH V2 16/18] be2iscsi: Fix possible reentrancy issue in be_iopoll Jayamohan Kallickal
2013-05-02 15:20   ` James Bottomley [this message]
2013-04-06  3:38 ` [PATCH V2 17/18] be2iscsi: Fix issue in passing the exp_cmdsn and max_cmdsn Jayamohan Kallickal
2013-04-06  3:38 ` [PATCH V2 18/18] be2iscsi: Bump the driver version Jayamohan Kallickal
2013-04-06  3:38 ` be2iscsi: Patchset for be2iscsi Jayamohan Kallickal
2013-04-12 21:08   ` Mike Christie

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=1367508048.3133.2.camel@dabdike \
    --to=jbottomley@parallels.com \
    --cc=jayamohank@gmail.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=michaelc@cs.wisc.edu \
    --cc=shlomop@mellanox.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