linux-kernel - [RFC PATCH 0/2] tracing: The Grinch who stole the stealing of Christmas

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]

Message-ID: <20141213004830.792da019@gandalf.local.home>
Date:	Sat, 13 Dec 2014 00:48:30 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Thomas Gleixner <tglx@...utronix.de>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Jiang Liu <jiang.liu@...ux.intel.com>, x86@...nel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Tony Luck <tony.luck@...el.com>,
	Borislav Petkov <bp@...en8.de>, Joerg Roedel <joro@...tes.org>,
	Marc Zyngier <marc.zyngier@....com>,
	Yinghai Lu <yinghai@...nel.org>,
	Alex Williamson <alex.williamson@...hat.com>
Subject: [RFC PATCH 0/2] tracing: The Grinch who stole the stealing of
 Christmas

On Fri, 12 Dec 2014 18:14:20 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Fri, 12 Dec 2014 21:35:14 +0100 (CET)
> Thomas Gleixner <tglx@...utronix.de> wrote:
> 
> 
> > We're almost there with x86 but my gut feeling tells me that pushing
> > it now is too risky. I rather prefer quiet holidays for all of us than
> > the nagging fear that the post holiday inbox will be full of obscure
> > bug reports and we then start a chase and bandaid race which will kill
> > the well earned recreation in an instant.
> 
> 
> > 
> >       Though one issue with that is, that for the early boot process
> >       there is no way to store that information as the tracer gets
> >       enabled way after init_IRQ(). But there is no reason why the
> >       tracer could not be enabled before that. All it needs is a
> >       working memory allocator. Steven?
> > 
> >       Now there is another class of problems which might be hard to
> >       debug. When the machine just boots into a hang, so we dont get a
> >       ftrace output neither from an oops nor from a console. It would
> >       be nice if we could have a command line option which prints
> >       enabled trace points via (early_)printk. That would avoid
> >       sending out ad hoc printk debug patches which will basically
> >       provide the same information as the trace_points. That would be
> >       useful for other hard to debug boot hangs as well. Steven?
> 
> Sure sure, everyone gets a nice calm xmas except for poor Steven who
> has to hack on early tracepoints such that this will be ready for 3.20!
> 
> -- Steve (The Grinch who Hacked on Christmas)

I guess I can enjoy my Holiday.

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