All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: mhocko@kernel.org, "James E.J. Bottomley" <JBottomley@odin.com>
Cc: Dan Williams <dan.j.williams@intel.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
	Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH] scsi: fix scsi_error_handler vs. scsi_host_dev_release race
Date: Fri, 28 Aug 2015 08:40:38 +0200	[thread overview]
Message-ID: <55E00266.8030809@suse.de> (raw)
In-Reply-To: <1440699420-30499-1-git-send-email-mhocko@kernel.org>

On 08/27/2015 08:16 PM, mhocko@kernel.org wrote:
> From: Michal Hocko <mhocko@suse.com>
> 
> b9d5c6b7ef57 ("[SCSI] cleanup setting task state in
> scsi_error_handler()") has introduced a race between scsi_error_handler
> and scsi_host_dev_release resulting in the hang when the device goes
> away because scsi_error_handler might miss a wake up:
> 
> CPU0					CPU1
> scsi_error_handler			scsi_host_dev_release
>   					  kthread_stop()
>   kthread_should_stop()
>     test_bit(KTHREAD_SHOULD_STOP)
> 					    set_bit(KTHREAD_SHOULD_STOP)
> 					    wake_up_process()
> 					    wait_for_completion()
> 
>   set_current_state(TASK_INTERRUPTIBLE)
>   schedule()
> 
> The most straightforward solution seems to be to invert the ordering of
> the set_current_state and kthread_should_stop.
> 
> The issue has been noticed during reboot test on a 3.0 based kernel but
> the current code seems to be affected in the same way.
> 
> Cc: stable # 3.6+
> Reported-and-Debugged-by: Mike Mayer <Mike.Meyer@teradata.com>
> Signed-off-by: Michal Hocko <mhocko@suse.com>
> ---
>  drivers/scsi/scsi_error.c | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/scsi/scsi_error.c b/drivers/scsi/scsi_error.c
> index 6457a8a0db9c..2c0a817d5dbe 100644
> --- a/drivers/scsi/scsi_error.c
> +++ b/drivers/scsi/scsi_error.c
> @@ -2169,8 +2169,11 @@ int scsi_error_handler(void *data)
>  	 * We never actually get interrupted because kthread_run
>  	 * disables signal delivery for the created thread.
>  	 */
> -	while (!kthread_should_stop()) {
> +	while (true) {
>  		set_current_state(TASK_INTERRUPTIBLE);
> +		if (kthread_should_stop())
> +			break;
> +
>  		if ((shost->host_failed == 0 && shost->host_eh_scheduled == 0) ||
>  		    shost->host_failed != atomic_read(&shost->host_busy)) {
>  			SCSI_LOG_ERROR_RECOVERY(1,
> 
Reviewed-by: Hannes Reinecke <hare@suse.de>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		               zSeries & Storage
hare@suse.de			               +49 911 74053 688
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: F. Imendörffer, J. Smithard, J. Guild, D. Upmanyu, G. Norton
HRB 21284 (AG Nürnberg)

  parent reply	other threads:[~2015-08-28  6:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-27 18:16 [PATCH] scsi: fix scsi_error_handler vs. scsi_host_dev_release race mhocko
2015-08-27 18:28 ` Dan Williams
2015-08-28  6:40 ` Hannes Reinecke [this message]
2015-08-28 14:56 ` James Bottomley
2015-08-28 15:17   ` Michal Hocko

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=55E00266.8030809@suse.de \
    --to=hare@suse.de \
    --cc=JBottomley@odin.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mhocko@suse.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.