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: <CAOesGMiLOcC2KR4b9Jq=hJT=8NKK95itWx0BsX7NGsmBYYLbSw@mail.gmail.com>
Date:	Wed, 26 Mar 2014 14:54:11 -0700
From:	Olof Johansson <olof@...om.net>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Tom Zanussi <tom.zanussi@...ux.intel.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [GIT PULL] tracing: Fix traceon trigger condition to actually
 turn tracing on

On Wed, Mar 26, 2014 at 2:21 PM, Steven Rostedt <rostedt@...dmis.org> wrote:
> Bah, I forgot to Cc LKML on my pull request. Doing this from a
> conference with very poor internet access from a laptop that I don't
> usually develop on, means I might make mistakes.
>
> On Wed, 2014-03-26 at 13:19 -0500, Tom Zanussi wrote:
>> On Wed, 2014-03-26 at 09:17 -0400, Steven Rostedt wrote:
>> > Linus,
>> >
>> > While on my flight to Linux Collaboration Summit, I was working on
>> > my slides for the event trigger tutorial. I booted a 3.14-rc7 kernel
>> > to perform what I wanted to teach and cut and paste it into my slides.
>> > When I tried the traceon event trigger with a condition attached to it
>> > (turns tracing on only if a field of the trigger event matches a condition
>> > set by the user), nothing happened. Tracing would not turn on. I stopped
>> > working on my presentation in order to find what was wrong.
>> >
>>
>> Hi Steve,
>>
>> Sorry you had to stop working on your presentation to dig into this -
>> thanks for doing that though - it looks correct and fixes the problem
>> here for me, so you can add my Tested-by:
>>
>> Tested-by: Tom Zanussi <tom.zanussi@...ux.intel.com>
>
> Linus already pulled it. But Olof came to me at lunch to tell me my
> patch broke his PA Semi PPC box.
>
> Olof, as you well know, I also own one of those beasts, and I just
> booted the kernel with that patch and all works fine. Perhaps its a
> config issue? Can you send me your config.


I think it's a side effect, and something else is going on. If I build
an boot a ppc64_defconfig on the box (I mistakenly told you that it
was pasemi_defconfig), it hangs early during boot during PCI init,
halfway through printing a line of stack usage warning.

However, it seems fickle. If I disable the hung task detector it seems
to go away, for example. So, I think something else is going on and it
just happened to align the stars for it to happen.

I'll keep trying to change variables enough to see what's going on. I
really wish I still had JTAG access on this box, but all those tools
are since long gone and forgotten. The conference wifi makes it harder
to work on this too, as I'm sure you've noticed...

Don't let this hold up anything at this time, unless someone else complains.


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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ