linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <Bart.VanAssche@sandisk.com>
To: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"bergwolf@gmail.com" <bergwolf@gmail.com>
Cc: "jejb@linux.vnet.ibm.com" <jejb@linux.vnet.ibm.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>
Subject: Re: [PATCH RFC] scsi: wait sd probing in manual scan
Date: Wed, 3 May 2017 18:15:02 +0000	[thread overview]
Message-ID: <1493835300.3901.28.camel@sandisk.com> (raw)
In-Reply-To: <1493365699-25566-1-git-send-email-bergwolf@gmail.com>

On Fri, 2017-04-28 at 15:48 +0800, Peng Tao wrote:
> We have a guest init programe trying to mount a device after doing scsi host scan
> at boot time. Occasionally it fails to find the device when mounting. After digging
> a bit, it seems the root cause is sd async_schedule probing.
> 
> With async probing, there is no guarantee of device readiness when scsi host
> scan finishes. However, users do expect to have a valid way to make sure device
> is usable. Change scsi scan to wait sd probing in manual scan case so that we
> don't leave user with random device state when scsi host scan returns.
> 
> Is this the right way to have such guarantee?

Hello Peng,

Please fix the guest init program such that it waits until the SCSI device
it needs is ready.

Thanks,

Bart.

      reply	other threads:[~2017-05-03 18:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28  7:48 [PATCH RFC] scsi: wait sd probing in manual scan Peng Tao
2017-05-03 18:15 ` Bart Van Assche [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=1493835300.3901.28.camel@sandisk.com \
    --to=bart.vanassche@sandisk.com \
    --cc=bergwolf@gmail.com \
    --cc=jejb@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.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;
as well as URLs for NNTP newsgroup(s).