From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>
Cc: Grygorii Strashko <grygorii.strashko@ti.com>,
stern@rowland.harvard.edu, linux-pm@vger.kernel.org,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH v2] PM / sleep: prohibit devices probing during suspend/hibernation
Date: Thu, 5 Nov 2015 18:07:45 -0800 [thread overview]
Message-ID: <20151106020745.GA24550@kroah.com> (raw)
In-Reply-To: <5530449.00gvFOj9K4@vostro.rjw.lan>
On Fri, Nov 06, 2015 at 03:04:10AM +0100, Rafael J. Wysocki wrote:
> On Thursday, November 05, 2015 04:09:57 PM Greg Kroah-Hartman wrote:
> > On Thu, Nov 05, 2015 at 11:38:23PM +0100, Rafael J. Wysocki wrote:
> > > On Monday, November 02, 2015 02:25:00 AM Rafael J. Wysocki wrote:
> > > > On Monday, October 19, 2015 11:54:24 PM Grygorii Strashko wrote:
> > > > > It is unsafe [1] if probing of devices will happen during suspend or
> > > > > hibernation and system behavior will be unpredictable in this case
> > > > > (for example: after successful probe the device potentially has a different
> > > > > set of PM callbacks than before [2]).
> > > > > So, let's prohibit device's probing in dpm_prepare() and defer their
> > > > > probes instead. The normal behavior will be restored in dpm_complete().
> > > > >
> > > > > This patch introduces new DD core APIs:
> > > > > device_defer_all_probes_enable()
> > > > > It will disable probing of devices and defer their probes.
> > > > > device_defer_all_probes_disable()
> > > > > It will restore normal behavior and trigger re-probing of deferred
> > > > > devices.
> > > > >
> > > > > [1] https://lkml.org/lkml/2015/9/11/554
> > > > > [2] https://lkml.org/lkml/2015/9/15/1039
> > > > > Cc: Alan Stern <stern@rowland.harvard.edu>
> > > > > Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
> > > > > Cc: Thierry Reding <thierry.reding@gmail.com>
> > > > > Signed-off-by: Grygorii Strashko <grygorii.strashko@ti.com>
> > > >
> > > > Greg, any objections against this one?
> > >
> > > Greg, if this isn't problematic, I'd still like to take it for v4.4.
> >
> > What? The merge window for new stuff closed a few weeks ago, how can
> > you add this for 4.4 when it needs to be in linux-next for a while
> > first?
>
> Well, it's not really scary and it was posted way before the merge window,
> but no one has had the time to look at it since then, apparently.
>
> Of course, I can queue it up for the next release too.
That would be best, thanks.
greg k-h
next prev parent reply other threads:[~2015-11-06 2:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 20:54 [PATCH v2] PM / sleep: prohibit devices probing during suspend/hibernation Grygorii Strashko
2015-11-02 1:25 ` Rafael J. Wysocki
2015-11-05 22:38 ` Rafael J. Wysocki
2015-11-06 0:09 ` Greg Kroah-Hartman
2015-11-06 2:04 ` Rafael J. Wysocki
2015-11-06 2:07 ` Greg Kroah-Hartman [this message]
2015-11-06 22:45 ` Rafael J. Wysocki
2015-11-05 22:19 ` Pavel Machek
2015-11-06 0:13 ` Rafael J. Wysocki
2015-11-06 9:58 ` Grygorii Strashko
2015-11-06 22:44 ` Rafael J. Wysocki
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=20151106020745.GA24550@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=grygorii.strashko@ti.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rjw@rjwysocki.net \
--cc=stern@rowland.harvard.edu \
--cc=thierry.reding@gmail.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).