From: Andrew Morton <akpm@linux-foundation.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Linux-pm mailing list <linux-pm@lists.osdl.org>,
"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: s2ram: warn when interrupts should be disabled but are not
Date: Mon, 14 Apr 2008 23:48:40 -0700 [thread overview]
Message-ID: <20080414234840.917594ea.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080412095311.GA1729@elf.ucw.cz>
On Sat, 12 Apr 2008 11:53:11 +0200 Pavel Machek <pavel@ucw.cz> wrote:
>
> sysdevs should be suspended/resumed with IRQs disabled; if something
> reenables them by mistake, we want to know early.
>
> Signed-off-by: Pavel Machek <pavel@suse.cz>
>
> ---
> commit fc3bccaf69e6c05464e7154369639bd5c96ccdc1
> tree bf960093ddb840242a00b4ec456ec79472b1c2ad
> parent 308e9d5309f378209e931f63f729806ec0a4d9f1
> author Pavel <pavel@amd.ucw.cz> Sat, 12 Apr 2008 11:52:05 +0200
> committer Pavel <pavel@amd.ucw.cz> Sat, 12 Apr 2008 11:52:05 +0200
>
> drivers/ata/ahci.c | 2 +-
> drivers/base/sys.c | 3 +++
> 2 files changed, 4 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/base/sys.c b/drivers/base/sys.c
> index 8e13fd9..e214467 100644
> --- a/drivers/base/sys.c
> +++ b/drivers/base/sys.c
> @@ -22,6 +22,7 @@ #include <linux/string.h>
> #include <linux/pm.h>
> #include <linux/device.h>
> #include <linux/mutex.h>
> +#include <linux/hardirq.h>
>
> #include "base.h"
>
> @@ -367,6 +368,7 @@ int sysdev_suspend(pm_message_t state)
> /* Call auxillary drivers first */
> list_for_each_entry(drv, &cls->drivers, entry) {
> if (drv->suspend) {
> + WARN_ON(!irqs_disabled());
> ret = drv->suspend(sysdev, state);
> if (ret)
> goto aux_driver;
Is this warning ever triggers I expect we'll really really wish that
we'd done the check _after_ calling drv->suspend, and that we had also
done a print_symbol(drv->suspend). No?
> @@ -442,6 +444,7 @@ int sysdev_resume(void)
> list_for_each_entry(sysdev, &cls->kset.list, kobj.entry) {
> pr_debug(" %s\n", kobject_name(&sysdev->kobj));
>
> + WARN_ON(!irqs_disabled());
> __sysdev_resume(sysdev);
> }
> }
Perhaps here too.
prev parent reply other threads:[~2008-04-15 6:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 9:53 s2ram: warn when interrupts should be disabled but are not Pavel Machek
2008-04-12 15:36 ` [linux-pm] " Alan Stern
2008-04-12 19:11 ` Pavel Machek
2008-04-14 5:24 ` David Brownell
2008-04-15 6:48 ` Andrew Morton [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=20080414234840.917594ea.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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