linux-kernel - Re: Tracing configuration review

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]

Date:	Sun, 13 Jun 2010 22:41:30 -0400
From:	Chase Douglas <chase.douglas@...onical.com>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Prasad <prasad@...ux.vnet.ibm.com>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Eduard - Gabriel Munteanu <eduard.munteanu@...ux360.ro>,
	Soeren Sandmann <sandmann@...mi.au.dk>,
	Steven Rostedt <rostedt@...dmis.org>,
	Ingo Molnar <mingo@...hat.com>, linux-kernel@...r.kernel.org,
	kernel-team@...ts.ubuntu.com
Subject: Re: Tracing configuration review

On Fri, 2010-06-11 at 14:51 -0700, Randy Dunlap wrote:
> I'm a bit surprised by one (family) of kconfig symbols here:
> 
> PM_TRACE=y, PM_TRACE_RTC=y
> 
> That enables low-level kernel developer debugging code.
> 
> Other than that, the rest make sense to me.

We try to focus a lot on the laptop use case, and so we do a bit of work
on suspend/resume bugs. For those unaware, these options allow one to
save the very last PM event point inside the RTC. If a suspend dies we
may be able to get some good information on where it died using this
tool. The functionality has to be manually enabled at runtime, otherwise
the RTC would get scribbled over during every resume. Since it doesn't
have any impact in the general use case, we leave it enabled by default.
We already build too many test kernels for other types of bugs :).

Thanks,

-- Chase

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