linux-kernel - Re: [GIT PULL 00/12] perf tools fixes

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, 23 Sep 2011 16:12:54 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Arnaldo Carvalho de Melo <acme@...radead.org>
Cc:	linux-kernel@...r.kernel.org, Anton Blanchard <anton@...ba.org>,
	Darren Hart <dvhart@...ux.intel.com>,
	David Ahern <dsahern@...il.com>,
	"David S . Miller" <davem@...emloft.net>,
	Eric B Munson <emunson@...bm.net>,
	Frederic Weisbecker <fweisbec@...il.com>,
	Ian Munsie <imunsie@....ibm.com>, Ingo Molnar <mingo@...e.hu>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>,
	Mike Galbraith <efault@....de>,
	Paul Mackerras <paulus@...ba.org>,
	Pekka Enberg <penberg@...helsinki.fi>,
	Peter Zijlstra <peterz@...radead.org>,
	Robert Richter <robert.richter@....com>,
	Stephane Eranian <eranian@...gle.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	yrl.pp-manager.tt@...achi.com
Subject: Re: [GIT PULL 00/12] perf tools fixes

On Fri, Sep 23, 2011 at 2:25 PM, Arnaldo Carvalho de Melo
<acme@...radead.org> wrote:
>
> Sorry about the noise, there is a problem in the way the python binding
> is built, i.e. it should notice that the header changed and rebuild the
> python binding, I bet this was what made David not notice it :-\

Can you please make sure that gets fixed at some point too? No huge
hurry, it can wait for the next merge window, but bugs like that not
only cause this kind of stupid compile errors, they also cause really
odd "why doesn't it work" problems that people can spend tons and tons
of time debugging, because they don't really "exist" - they're just a
result of a stale object file that didn't get properly recompiled.

> You noticed it probably because it was the first build of the tool on
> your local repo or used a new O= output dir.

I do "git clean -dqfx" every once in a while (especially after having
done "make allmodconfig" builds before -rc releases etc), and I don't
recompile the perf tools very often. So yeah, this was the first build
after a cleanout event.

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