linux-kernel - Re: [PATCH][GIT PULL] trace,x86: Move creation of irq tracepoints from apic.c to irq.c

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:	Fri, 21 Jun 2013 17:26:07 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	LKML <linux-kernel@...r.kernel.org>
Cc:	"H. Peter Anvin" <hpa@...ux.intel.com>,
	Ingo Molnar <mingo@...nel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Seiji Aguchi <seiji.aguchi@....com>
Subject: Re: [PATCH][GIT PULL] trace,x86: Move creation of irq tracepoints
 from apic.c to irq.c

On Fri, 2013-06-21 at 17:09 -0400, Steven Rostedt wrote:
> On Fri, 2013-06-21 at 13:31 -0400, Steven Rostedt wrote:
> 
> > My testing also triggered another bug, but I'm not sure it's related to
> > these patches or something that already existed. I'm currently
> > investigating it now.
> 
> 
> I haven't been able to reproduce it.

Correction, I am able to reproduce it. The trick is I need to kick off
the test as soon as I get a login prompt, as the gui is still coming up
(this time the crash happened on pulseaudio). The test suite runs the
test when it detects the login. I was trying to reproduce it manually,
which was well after login was set up.

I'll try to make sure I can reproduce it consistently, or at least in a
short number of tries. And then remove all the patches and see if I can
still trigger it.

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