public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tomas Henzl <thenzl@redhat.com>
To: Sumit.Saxena@lsi.com, linux-scsi@vger.kernel.org
Cc: jbottomley@parallels.com, kashyap.desai@lsi.com, aradford@gmail.com
Subject: Re: [PATCH][SCSI] megaraid_sas: Fix synchronization problem between sysPD IO path and AEN path
Date: Thu, 17 Oct 2013 16:04:55 +0200	[thread overview]
Message-ID: <525FEE87.6070808@redhat.com> (raw)
In-Reply-To: <201310161134.r9GBYYqK021397@cosmhbs0.lsi.com>

On 10/16/2013 01:34 PM, Sumit.Saxena@lsi.com wrote:
> There is syncronization problem between sysPD IO path and AEN path. Driver maintains instance->pd_list[] array, which will get updated(by calling function megasas_get_pd_list[]), whenever any of below events occurs-

Hi Sumit,
- I'm a bit confused here- there are two threads which might access the same array, but the problem is still there
  when the second thread accesses the array during the final memcpy, I have expected that you will add some locking,
  but maybe I'm missing something.
- now the code zeroes the pd_list even when the 
  (ret == 0 && (ci->count < (MEGASAS_MAX_PD_CHANNELS * MEGASAS_MAX_DEV_PER_CHANNEL)))
  is not true. This is I think new - is that intentional?
Thanks, Tomas
 

>
>
>
>
>
>
> MR_EVT_PD_INSERTED
> MR_EVT_PD_REMOVED
> MR_EVT_CTRL_HOST_BUS_SCAN_REQUESTED
> MR_EVT_FOREIGN_CFG_IMPORTED
>
> At same time running sysPD IO will be accessing the same array instance->pd_list[], which is getting updated in AEN path, because
> of this IO may not get correct PD info from instance->pd_list[] array.
>
> Signed-off-by: Adam Radford <adam.radford@lsi.com>
> Signed-off-by: Sumit Saxena <sumit.saxena@lsi.com>
> ---
> diff --git a/drivers/scsi/megaraid/megaraid_sas.h b/drivers/scsi/megaraid/megaraid_sas.h
> index 0c73ba4..e9e543c 100644
> --- a/drivers/scsi/megaraid/megaraid_sas.h
> +++ b/drivers/scsi/megaraid/megaraid_sas.h
> @@ -1531,6 +1531,7 @@ struct megasas_instance {
>  	struct megasas_register_set __iomem *reg_set;
>  	u32 *reply_post_host_index_addr[MR_MAX_MSIX_REG_ARRAY];
>  	struct megasas_pd_list          pd_list[MEGASAS_MAX_PD];
> +	struct megasas_pd_list          local_pd_list[MEGASAS_MAX_PD];
>  	u8     ld_ids[MEGASAS_MAX_LD_IDS];
>  	s8 init_id;
>  
> diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c b/drivers/scsi/megaraid/megaraid_sas_base.c
> index e62ff02..83ebc75 100644
> --- a/drivers/scsi/megaraid/megaraid_sas_base.c
> +++ b/drivers/scsi/megaraid/megaraid_sas_base.c
> @@ -3194,21 +3194,23 @@ megasas_get_pd_list(struct megasas_instance *instance)
>  	     (le32_to_cpu(ci->count) <
>  		  (MEGASAS_MAX_PD_CHANNELS * MEGASAS_MAX_DEV_PER_CHANNEL))) {
>  
> -		memset(instance->pd_list, 0,
> +		memset(instance->local_pd_list, 0,
>  			MEGASAS_MAX_PD * sizeof(struct megasas_pd_list));
>  
>  		for (pd_index = 0; pd_index < le32_to_cpu(ci->count); pd_index++) {
>  
> -			instance->pd_list[le16_to_cpu(pd_addr->deviceId)].tid	=
> +			instance->local_pd_list[le16_to_cpu(pd_addr->deviceId)].tid	=
>  				le16_to_cpu(pd_addr->deviceId);
> -			instance->pd_list[le16_to_cpu(pd_addr->deviceId)].driveType	=
> +			instance->local_pd_list[le16_to_cpu(pd_addr->deviceId)].driveType	=
>  							pd_addr->scsiDevType;
> -			instance->pd_list[le16_to_cpu(pd_addr->deviceId)].driveState	=
> +			instance->local_pd_list[le16_to_cpu(pd_addr->deviceId)].driveState	=
>  							MR_PD_STATE_SYSTEM;
>  			pd_addr++;
>  		}
>  	}
>  
> +	memcpy(instance->pd_list, instance->local_pd_list,
> +		sizeof(instance->pd_list));
>  	pci_free_consistent(instance->pdev,
>  				MEGASAS_MAX_PD * sizeof(struct MR_PD_LIST),
>  				ci, ci_h);
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  parent reply	other threads:[~2013-10-17 14:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-16 11:34 [PATCH][SCSI] megaraid_sas: Fix synchronization problem between sysPD IO path and AEN path Sumit.Saxena
2013-10-16 21:44 ` James Bottomley
2013-10-17  4:15   ` Saxena, Sumit
2013-10-17 14:04 ` Tomas Henzl [this message]
2013-10-17 15:10   ` Saxena, Sumit
2013-10-17 15:48     ` Tomas Henzl
2013-10-17 16:05       ` Saxena, Sumit

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=525FEE87.6070808@redhat.com \
    --to=thenzl@redhat.com \
    --cc=Sumit.Saxena@lsi.com \
    --cc=aradford@gmail.com \
    --cc=jbottomley@parallels.com \
    --cc=kashyap.desai@lsi.com \
    --cc=linux-scsi@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