public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Roland Dreier <roland@kernel.org>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Shaohua Li <shaohua.li@intel.com>,
	Arjan van de Ven <arjan@infradead.org>
Subject: Re: [PATCH] Revert "driver core: synchronize device shutdown"
Date: Tue, 4 Mar 2014 20:09:29 -0800	[thread overview]
Message-ID: <20140305040929.GA31130@kroah.com> (raw)
In-Reply-To: <1393991871-1743-1-git-send-email-roland@kernel.org>

On Tue, Mar 04, 2014 at 07:57:51PM -0800, Roland Dreier wrote:
> From: Roland Dreier <roland@purestorage.com>
> 
> This reverts commit 401097ea4b89846d66ac78f7f108d49c2e922d9c.  The
> original changelog said:
> 
>     A patch series to make .shutdown execute asynchronously.  Some drivers's
>     shutdown can take a lot of time.  The patches can help save some shutdown
>     time.  The patches use Arjan's async API.
> 
>     This patch:
> 
>     synchronize all tasks submitted by .shutdown
> 
> However, I'm not able to find any evidence that any other patches from
> this series were applied, nor am I able to find any async tasks that are
> scheduled in a .shutdown context.
> 
> On the other hand, we see occasional hangs on shutdown that appear to be
> caused by the async_synchronize_full() in device_shutdown() waiting
> forever for the async probing in sd if a SCSI disk shows up at just the
> wrong time — the system starts the probe, but begins shutting down and
> tears down too much of the SCSI driver to finish the probe.
> 
> If we had any async shutdown tasks, I guess the right fix would be to
> create a "shutdown" async domain and have device_shutdown() only wait
> for that domain.  But since there apparently are no async shutdown
> tasks, we can just revert the waiting.
> 
> Signed-off-by: Roland Dreier <roland@purestorage.com>

Hm, no one seems to have said anything for the past 5 years about this.

Shaohua and Arjan, any objection to this being applied?

thanks,

greg k-h

  reply	other threads:[~2014-03-05  4:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-05  3:57 [PATCH] Revert "driver core: synchronize device shutdown" Roland Dreier
2014-03-05  4:09 ` Greg Kroah-Hartman [this message]
2014-03-05  4:15   ` Roland Dreier
2014-03-05  4:38     ` Greg Kroah-Hartman
2014-03-08  2:30       ` Arjan van de Ven
2014-03-09  6:02         ` Greg Kroah-Hartman

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=20140305040929.GA31130@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=roland@kernel.org \
    --cc=shaohua.li@intel.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