Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1292499

RE: [PATCH] bnx2fc:Add proper locking protection in bnx2fc_ctrlr_enabled

From Joe Carnuccio <joe.carnuccio@qlogic.com>
Newsgroups linux.kernel
Subject RE: [PATCH] bnx2fc:Add proper locking protection in bnx2fc_ctrlr_enabled
Date 2015-12-15 21:00 +0100
Message-ID <qG3Vo-aC-13@gated-at.bofh.it> (permalink)
References <qG0Xw-6KR-25@gated-at.bofh.it> <qG0Xw-6KR-23@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


Also, the patch fails to do what it's message describes, i.e. the calls _bnx2fc_enable() and _bnx2fc_disable() are outside the lock/unlock.


-----Original Message-----
From: Chad Dupuis 
Sent: Tuesday, December 15, 2015 8:43 AM
To: Nicholas Krause <xerofoify@gmail.com>
Cc: Dept-Eng QLogic Storage Upstream <QLogic-Storage-Upstream@qlogic.com>; JBottomley@odin.com; martin.petersen@oracle.com; linux-scsi <linux-scsi@vger.kernel.org>; linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] bnx2fc:Add proper locking protection in bnx2fc_ctrlr_enabled


On Sat, 12 Dec 2015, Nicholas Krause wrote:

> This adds proper locking protection in bnx2fc_ctrl_enabled around the 
> calls to the functions, _bnx2fc_enable and _bnx2fc_disable in order to 
> avoid concurrent access on these functions accessing global referenced 
> data structures in their internal intended work.
>
> Signed-off-by: Nicholas Krause <xerofoify@gmail.com>
> ---
> drivers/scsi/bnx2fc/bnx2fc_fcoe.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c 
> b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> index 67405c6..e43648f 100644
> --- a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> +++ b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
> @@ -2177,13 +2177,21 @@ static int bnx2fc_ctlr_enabled(struct 
> fcoe_ctlr_device *cdev) {
> 	struct fcoe_ctlr *ctlr = fcoe_ctlr_device_priv(cdev);
>
> +	rtnl_lock();
> +	mutex_lock(&bnx2fc_dev_lock);
> 	switch (cdev->enabled) {
> 	case FCOE_CTLR_ENABLED:
> +		rtnl_unlock();
> +		mutex_unlock(&bnx2fc_dev_lock);
> 		return __bnx2fc_enable(ctlr);
> 	case FCOE_CTLR_DISABLED:
> +		rtnl_unlock();
> +		mutex_unlock(&bnx2fc_dev_lock);
> 		return __bnx2fc_disable(ctlr);
> 	case FCOE_CTLR_UNUSED:
> 	default:
> +		rtnl_unlock();
> +		mutex_unlock(&bnx2fc_dev_lock);
> 		return -ENOTSUPP;
> 	};
> }
>

Nack.  All we end up protecting is the check of cdev->enabled and I do not believe taking two mutexes is required for that.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | NextPrevious in thread | Find similar | Unroll thread


Thread

Re: [PATCH] bnx2fc:Add proper locking protection in  bnx2fc_ctrlr_enabled Chad Dupuis <chad.dupuis@qlogic.com> - 2015-12-15 17:50 +0100
  RE: [PATCH] bnx2fc:Add proper locking protection in  bnx2fc_ctrlr_enabled Joe Carnuccio <joe.carnuccio@qlogic.com> - 2015-12-15 21:00 +0100

csiph-web