linux-kernel - Re: ftraced and suspend to ram

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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 21 Aug 2008 20:37:10 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Nigel Cunningham <nigel@...el.suspend2.net>,
	Pavel Machek <pavel@....cz>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: ftraced and suspend to ram

On Thursday, 21 of August 2008, Steven Rostedt wrote:
> 
> On Thu, 21 Aug 2008, Rafael J. Wysocki wrote:
> 
> > On Thursday, 21 of August 2008, Steven Rostedt wrote:
> > > 
> > > In latest 2.6.27(git) enabling dynamic ftrace makes resume from a suspend 
> > > to ram reboot instead of resuming. Queued for 2.6.28 is a new method of 
> > > recording mcount callers at compile time that does not have this issue.
> > > 
> > > But the new method is still too "green" to be pulled into 27, so the old 
> > > ftraced (daemon method) needs to be fixed for 27.
> > > 
> > > The way dynamic ftrace works with the daemon method is this. On boot up 
> > > the mcount function simply returns. When ftrace is initialized, it calls 
> > > kstop_machine to modify the mcount function to call another function 
> > > called "ftrace_record_ip". This new function will record in a preallocated 
> > > hash (allocated by the ftrace initializer) all the callers of mcount. A 
> > > check is made to see if the caller has already been put into the hash, and 
> > > if so, it is not recorded again.
> > > 
> > > Later on a kernel thread ftraced is created. This kernel thread wakes up 
> > > once a second and checks to see if any new functions were added to the 
> > > hash. If so, it then calls kstop_machine and modifies those callers to 
> > > mcount into nops.
> > > 
> > > Again, this daemon method makes resume from suspend to ram reboot instead 
> > > of resuming. Now, I'm asking the s2r gurus, what did I miss? Do I need to 
> > > add a "NO_FREEZE" flag or something to the "ftraced" kernel thread?
> > > 
> > > Just asking for some advice.
> > 
> > If I'm not mistaken, it'll probably suffice to make it freezable, so that it
> > doesn't run while the system is suspending and resuming.  Would that be
> > acceptable?
> 
> Does it not freeze by default.

No, it doesn't.  Kernel threads are not freezable by default

> > Please tell me where exactly the ftraced source code is located.
> 
> It's in Linus's latest git tree.
> 
> The code in question is the ftraced() function in kernel/trace/ftrace.c

Thanks, I'll have a look in a while.

Rafael
--
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/