linux-kernel - Re: Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <6553656.pcJl3UFpb6@vostro.rjw.lan>
Date:	Fri, 30 Jan 2015 01:53:25 +0100
From:	"Rafael J. Wysocki" <rjw@...ysocki.net>
To:	Pavel Machek <pavel@....cz>
Cc:	"Liu, Chuansheng" <chuansheng.liu@...el.com>,
	"Fu, Zhonghui" <zhonghui.fu@...ux.intel.com>,
	"Brown, Len" <len.brown@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"linux-pm@...r.kernel.org" <linux-pm@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	trivial@...nel.org
Subject: Re: Change behaviour when tracing ... nasty trap (was Re: [PATCH] PM/Trace: get rid of synchronous resume limit during PM trace)

On Monday, January 26, 2015 02:43:04 PM Pavel Machek wrote:
> Document pm_tracing actually affecting suspend in non-trivial way.
> 
> 
> Signed-off-by: Pavel Machek <pavel@....cz>
> 
> ---
> 
> On Mon 2015-01-26 14:41:02, Rafael J. Wysocki wrote:
> > On Monday, January 26, 2015 12:05:16 PM Pavel Machek wrote:
> > > On Mon 2015-01-26 10:39:04, Liu, Chuansheng wrote:
> 
> > > > > > @@ -517,8 +517,7 @@ static int device_resume_noirq(struct device *dev,
> > > > > pm_message_t state, bool asyn
> > > > > >
> > > > > >  static bool is_async(struct device *dev)
> > > > > >  {
> > > > > > -	return dev->power.async_suspend && pm_async_enabled
> > > > > > -		&& !pm_trace_is_enabled();
> > > > > > +	return dev->power.async_suspend && pm_async_enabled;
> > > > > >  }
> > > > > >
> > > > > 
> > > > > Actually... whoever did the original patch was evil person. Changing
> > > > > behaviour when tracing is requested is evil, evil, evil. Git blame
> > > > > tells me
> > > > > 
> > > > > Signed-off-by: Chuansheng Liu <chuansheng.liu@...el.com>
> > > > > 
> > > > > went to the dark side.
> > > > 
> > > > Although I didn't get where is something wrong, but the is_async() is not created by my commit,
> > > > it is from commit (PM: Start asynchronous resume threads upfront), I just moved it ahead.
> > > > 
> > > > And like other phases, I added it into resum/suspend_noirq()...
> > > 
> > > I see, blame blamed wrong person. It looks like Rafael is evil:
> > > 
> > > commit 97df8c12995c5bac73e3bfeea4c5be155c1f4401
> > > Author: Rafael J. Wysocki <rjw@...k.pl>
> > > Date:   Sat Jan 23 22:25:31 2010 +0100
> > > 
> > >     PM: Start asynchronous resume threads upfront
> > 
> > This only means we won't use asyc suspend/resume at all when the RTC-based
> > resume debug is enabled, because it wouldn't make sense (the RTC-based
> > debug requires strict ordering of callbacks between devices or we may find
> > that device A hanged the resume while actually device B that was running in
> > parallel with A did that).
> > 
> > And I shouldn't even need to explain this ...  Sad.
> 
> Well, I forgot that pm_trace_is_enabled() is the simple, RTC based
> one, and believe it would be worth a comment...

A comment won't hurt. :-)

Applied, thanks!

> diff --git a/Documentation/power/s2ram.txt b/Documentation/power/s2ram.txt
> index 1bdfa04..4685aee 100644
> --- a/Documentation/power/s2ram.txt
> +++ b/Documentation/power/s2ram.txt
> @@ -69,6 +69,10 @@ Reason for this is that the RTC is the only reliably available piece of
>  hardware during resume operations where a value can be set that will
>  survive a reboot.
>  
> +pm_trace is not compatible with asynchronous suspend, so it turns
> +asynchronous suspend off (which may work around timing or
> +ordering-sensitive bugs).
> +
>  Consequence is that after a resume (even if it is successful) your system
>  clock will have a value corresponding to the magic number instead of the
>  correct date/time! It is therefore advisable to use a program like ntp-date
> 
> 
> 

-- 
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/