From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Sahitya Tummala <stummala@codeaurora.org>
Cc: "Rafael J. Wysocki\"" <rjw@rjwysocki.net>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PM: Fix bug in the error handling of async suspend
Date: Thu, 08 Dec 2016 01:18:59 +0100 [thread overview]
Message-ID: <3147015.xntCBFhHqr@aspire.rjw.lan> (raw)
In-Reply-To: <1481121632-17466-1-git-send-email-stummala@codeaurora.org>
On Wednesday, December 07, 2016 08:10:32 PM Sahitya Tummala wrote:
> If async_suspend is enabled for parent and child devices, then
> PM framework has to ensure that parent's async suspend gets called
> only after child's async suspend is done. In case if child's async
> suspend fails with error, then parent's async suspend must not be
> invoked. The current code uses async_error to ensure this but there
> is a problem with it in __device_suspend(). This function notifies
> the completion of child's async suspend before updating its error
> via async_error variable. As a result, parent's async suspend gets
> invoked even though it's child suspend has failed. Fix this bug by
> updating the async_error before notifying the child's completion.
>
> Signed-off-by: Sahitya Tummala <stummala@codeaurora.org>
> ---
> drivers/base/power/main.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/base/power/main.c b/drivers/base/power/main.c
> index e44944f4be77..f733f50f8321 100644
> --- a/drivers/base/power/main.c
> +++ b/drivers/base/power/main.c
> @@ -1460,9 +1460,9 @@ static int __device_suspend(struct device *dev, pm_message_t state, bool async)
> dpm_watchdog_clear(&wd);
>
> Complete:
> - complete_all(&dev->power.completion);
> if (error)
> async_error = error;
> + complete_all(&dev->power.completion);
>
> TRACE_SUSPEND(error);
> return error;
Good catch!
I'm queuing this one up (with some whitespace rearrangements).
Thanks,
Rafael
prev parent reply other threads:[~2016-12-08 0:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 14:40 Sahitya Tummala
2016-12-08 0:18 ` Rafael J. Wysocki [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=3147015.xntCBFhHqr@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=stummala@codeaurora.org \
/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
all inboxes | Powered by JetHome®