linux-kernel - Re: [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates

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: <20111012081629.GA25086@elte.hu>
Date:	Wed, 12 Oct 2011 10:16:29 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	Frederic Weisbecker <fweisbec@...il.com>
Subject: Re: [PATCH 0/2 v2] [GIT PULL][v3.2] tracing: queued updates


* Steven Rostedt <rostedt@...dmis.org> wrote:

> 
> Ingo,
> 
> I found the build bug with ftrace disabled. It was in the second to last
> patch of the series. It was a cut and paste error where the ftrace_is_dead()
> stub had "extern static inline" which caused the error.
> 
> I rebased and pushed to my git tree. Please check the SHA1, even though
> the mirrors should be updated by now.
> 
> I tested this branch with the following:
> 
>  allnoconfig + minconfig to boot
> 
>  full ftrace enabled to boot and test
> 
>  ftrace without function tracing to boot and test
> 
>  no tracing enabled to boot and test
> 
>  allmodconfig to boot and test - a call trace dumped from a non
>   related bug (in slub). I will investigate this later.
> 
>  allyesconfig to build - just made sure it builds.
> 
> I'm only sending out the last two patches as the other patches are
> still the same. The rebase started from the second patch.
> 
> -- Steve
> 
> Please pull the latest tip/perf/core tree, which can be found at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git
> tip/perf/core
> 
> Head SHA1: d696b58ca2c3ca76e784ef89a7e0453d9b7ab187

Hm, even after 12+ hours of wait i can only pull 177e216 from your 
tip/perf/core. Is this a korg delay, or did you forget to push? The 
perf/urgent branch was there, so i don't think it's korg delay.

Thanks,

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