From: Kashyap Desai <kashyap.desai@avagotech.com>
To: Tomas Henzl <thenzl@redhat.com>,
Sumit Saxena <sumit.saxena@avagotech.com>,
linux-scsi@vger.kernel.org
Cc: martin.petersen@oracle.com, hch@infradead.org,
jbottomley@parallels.com, aradford@gmail.com
Subject: RE: [PATCH 3/7] megaraid_sas : Do not process IOCTLs and SCSI commands during driver removal
Date: Thu, 13 Nov 2014 13:05:21 +0530 [thread overview]
Message-ID: <370f46a365d1cdc3eb42242ec287f6e4@mail.gmail.com> (raw)
In-Reply-To: 4e1d4dfe448d9ed6c275bfea6b9203ac@mail.gmail.com
> -----Original Message-----
> From: Kashyap Desai [mailto:kashyap.desai@avagotech.com]
> Sent: Wednesday, November 12, 2014 4:39 PM
> To: 'Tomas Henzl'; Sumit Saxena; 'linux-scsi@vger.kernel.org'
> Cc: 'martin.petersen@oracle.com'; 'hch@infradead.org';
> 'jbottomley@parallels.com'; 'aradford@gmail.com'
> Subject: RE: [PATCH 3/7] megaraid_sas : Do not process IOCTLs and SCSI
> commands during driver removal
>
>
>
> > -----Original Message-----
> > From: Tomas Henzl [mailto:thenzl@redhat.com]
> > Sent: Tuesday, November 11, 2014 7:13 PM
> > To: Sumit.Saxena@avagotech.com; linux-scsi@vger.kernel.org
> > Cc: martin.petersen@oracle.com; hch@infradead.org;
> > jbottomley@parallels.com; kashyap.desai@avagotech.com;
> > aradford@gmail.com
> > Subject: Re: [PATCH 3/7] megaraid_sas : Do not process IOCTLs and SCSI
> > commands during driver removal
> >
> > On 11/10/2014 01:21 PM, Sumit.Saxena@avagotech.com wrote:
> > > Do not process any SCSI and IOCTL command further(return them with
> > > appropriate return values to callers), while driver removal is in
> > > progress/PCI
> > shutdown is invoked.
> > >
> > > Signed-off-by: Sumit Saxena <sumit.saxena@avagotech.com>
> > > Signed-off-by: Kashyap Desai <kashyap.desai@avagotech.com>
> > > ---
> > > drivers/scsi/megaraid/megaraid_sas_base.c | 20 ++++++++++++++++--
> --
> > > 1 files changed, 16 insertions(+), 4 deletions(-)
> > >
> > > diff --git a/drivers/scsi/megaraid/megaraid_sas_base.c
> > > b/drivers/scsi/megaraid/megaraid_sas_base.c
> > > index f6a69a3..7754eeb 100644
> > > --- a/drivers/scsi/megaraid/megaraid_sas_base.c
> > > +++ b/drivers/scsi/megaraid/megaraid_sas_base.c
> > > @@ -1572,6 +1572,12 @@ megasas_queue_command(struct Scsi_Host
> > *shost, struct scsi_cmnd *scmd)
> > > instance = (struct megasas_instance *)
> > > scmd->device->host->hostdata;
> > >
> > > + if (instance->unload == 1) {
> > > + scmd->result = DID_NO_CONNECT << 16;
> > > + scmd->scsi_done(scmd);
> > > + return 0;
> > > + }
> > > +
> > > if (instance->issuepend_done == 0)
> > > return SCSI_MLQUEUE_HOST_BUSY;
> > >
> > > @@ -4957,10 +4963,6 @@ static int megasas_io_attach(struct
> > megasas_instance *instance)
> > > return -ENODEV;
> > > }
> > >
> > > - /*
> > > - * Trigger SCSI to scan our drives
> > > - */
> > > - scsi_scan_host(host);
> > > return 0;
> > > }
> > >
> > > @@ -5288,6 +5290,10 @@ retry_irq_register:
> > > goto fail_io_attach;
> > >
> > > instance->unload = 0;
> > > + /*
> > > + * Trigger SCSI to scan our drives
> > > + */
> > > + scsi_scan_host(host);
> > >
> > > /*
> > > * Initiate AEN (Asynchronous Event Notification) @@ -6051,6
> > > +6057,12 @@ megasas_mgmt_fw_ioctl(struct megasas_instance
> > *instance,
> > > megasas_issue_blocked_cmd(instance, cmd, 0);
> > > cmd->sync_cmd = 0;
> >
> > I've expected that you'll not send the command to the card, you first
> > issue blocked command and after that test unload state.
> > Shouldn't it be reversed?
> Actually, there was a two part of this Patch for IOCTL path. One will
not allow
> to send IOCTL while driver removal.
> Another will not use already return IOCTL from FW to avoid illegal
memory
> access on MFI frame.
> Driver wakeup all blocked command in unload path and MFI/MPT frames are
> freed as well, so this check is good to have.
>
> As you suggested, we missed to have another check in IOCTL path, before
> driver takes semaphore. It was planned, but somehow we missed while
> submitting this patch set.
> We will send incremental patch for that part.
Correction - First of all sorry for confusion.
megasas_mgmt_ioctl_fw and megasas_mgmt_ioctl_aen already has a check for
instance->unload. We don't need any changes for this patch.
Tomas -
We are planning to provide resend patch series which will have changes for
below two patch.
[PATCH 1/7] megaraid_sas : Driver version upgrade and
[PATCH 4/7] megaraid_sas : Online Firmware upgrade support for Extended VD
feature
` Kashyap
>
> >
> > >
> > > + if (instance->unload == 1) {
> > > + dev_info(&instance->pdev->dev, "we are doing unload so no
> > need"
> > > + "to submit data to application. This may be force
exit"
> > > + "from driver\n");
> >
> > I'm not a native speaker, so I'll not comment on the wording, but you
> > should add a space at the line breaks.
>
> Agree. will address this part.
>
> > + dev_info(&instance->pdev->dev, "we are doing unload so no
> > need "
> > + "to submit data to application. This may be force
exit
> > "
> > + "from driver\n");
> >
> > > + goto out;
> > > + }
> > > /*
> > > * copy out the kernel buffers to user buffers
> > > */
> >
> > Aren't there other ioctl paths too - for example
> > megasas_mgmt_ioctl_aen - isn't a block needed there too?
> This path will be cleanup from megasas_shutdown_controller() call. AEN
> and MAP SYNC command will be aborted explicitly.
>
> >
prev parent reply other threads:[~2014-11-13 7:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 12:21 [PATCH 3/7] megaraid_sas : Do not process IOCTLs and SCSI commands during driver removal Sumit.Saxena
2014-11-11 13:42 ` Tomas Henzl
2014-11-12 11:08 ` Kashyap Desai
2014-11-13 7:35 ` Kashyap Desai [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=370f46a365d1cdc3eb42242ec287f6e4@mail.gmail.com \
--to=kashyap.desai@avagotech.com \
--cc=aradford@gmail.com \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sumit.saxena@avagotech.com \
--cc=thenzl@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.