From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Christof Schmitt <christof.schmitt@de.ibm.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, linux-s390@vger.kernel.org,
Martin Peschke <mp3@de.ibm.com>
Subject: Re: [patch 1/2] zfcp: Fix race during ERP thread shutdown
Date: Tue, 11 Mar 2008 17:43:41 +0100 [thread overview]
Message-ID: <20080311164341.GA6380@osiris.boeblingen.de.ibm.com> (raw)
In-Reply-To: <20080310152328.463410000@de.ibm.com>
> --- a/drivers/s390/scsi/zfcp_erp.c 2008-03-10 12:34:48.000000000 +0100
> +++ b/drivers/s390/scsi/zfcp_erp.c 2008-03-10 16:05:26.000000000 +0100
> @@ -1002,7 +1002,7 @@ zfcp_erp_thread_setup(struct zfcp_adapte
> &adapter->status));
> debug_text_event(adapter->erp_dbf, 5, "a_thset_ok");
> }
> -
> + atomic_set_mask(ZFCP_STATUS_ADAPTER_ERP_ACCEPT, &adapter->status);
> return (retval < 0);
This way the flag will be set even if the creation of the erp thread failed.
It should be done somewhere within zfcp_erp_thread() instead.
Besides that setting the flag must be done while holding the erp_lock.
Otherwise zfcp_erp_action_enqueue might check the flag, other cpu clears
the flag right after that, and then enqueueing continues while the flag is
not set.
> }
>
> @@ -1025,6 +1025,8 @@ zfcp_erp_thread_kill(struct zfcp_adapter
> {
> int retval = 0;
>
> + atomic_clear_mask(ZFCP_STATUS_ADAPTER_ERP_ACCEPT, &adapter->status);
> + zfcp_erp_wait(adapter);
> atomic_set_mask(ZFCP_STATUS_ADAPTER_ERP_THREAD_KILL, &adapter->status);
> up(&adapter->erp_ready_sem);
>
> @@ -2940,8 +2942,7 @@ zfcp_erp_action_enqueue(int action,
> * efficient.
> */
>
> - if (!atomic_test_mask(ZFCP_STATUS_ADAPTER_ERP_THREAD_UP,
> - &adapter->status))
> + if (!atomic_test_mask(ZFCP_STATUS_ADAPTER_ERP_ACCEPT, &adapter->status))
> return -EIO;
>
> debug_event(adapter->erp_dbf, 4, &action, sizeof (int));
> --- a/drivers/s390/scsi/zfcp_ccw.c 2008-03-10 12:34:48.000000000 +0100
> +++ b/drivers/s390/scsi/zfcp_ccw.c 2008-03-10 16:05:26.000000000 +0100
> @@ -198,7 +198,6 @@ zfcp_ccw_set_offline(struct ccw_device *
> down(&zfcp_data.config_sema);
> adapter = dev_get_drvdata(&ccw_device->dev);
> zfcp_erp_adapter_shutdown(adapter, 0);
> - zfcp_erp_wait(adapter);
> zfcp_erp_thread_kill(adapter);
And as a sidenote, if the scenario this patch is supposed to fix can really
happen, how can you make sure the adapter is still down before the erp thread
gets killed? Some action could have been enqueued and finished which reopened
the adapter after zfcp_erp_adapter_shutdown and before zfcp_erp_thread_kill.
Just wondering... :)
next prev parent reply other threads:[~2008-03-11 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 15:18 [patch 0/2] zfcp fixes Christof Schmitt
2008-03-10 15:18 ` [patch 1/2] zfcp: Fix race during ERP thread shutdown Christof Schmitt
2008-03-11 16:43 ` Heiko Carstens [this message]
2008-03-12 14:13 ` Martin Peschke
2008-03-17 14:19 ` Christof Schmitt
2008-03-17 14:23 ` James Bottomley
2008-03-17 14:29 ` Christof Schmitt
2008-03-10 15:18 ` [patch 2/2] zfcp: Fix handling for boxed port after physical close Christof Schmitt
2008-03-10 15:33 ` [patch 0/2] zfcp fixes James Bottomley
2008-03-10 16:26 ` Christof Schmitt
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=20080311164341.GA6380@osiris.boeblingen.de.ibm.com \
--to=heiko.carstens@de.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=christof.schmitt@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mp3@de.ibm.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