linux-kernel - Re: [GIT PULL] perf 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]

Message-ID: <20130912184341.GA11400@ghostprotocols.net>
Date:	Thu, 12 Sep 2013 15:43:41 -0300
From:	Arnaldo Carvalho de Melo <acme@...stprotocols.net>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Ingo Molnar <mingo@...nel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] perf fixes

Em Thu, Sep 12, 2013 at 11:10:37AM -0700, Linus Torvalds escreveu:
> On Thu, Sep 12, 2013 at 11:03 AM, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
> > When I compiled "perf" at the same time as doing a big kernel compile,
> > the kernel compile failed

> Oops. That may actually have been me being a bit *too* eager with a
> "make allmodconfig" build. I can't reproduce it, and I'm starting to
> suspect that I instead had two kernel compiles going, not one kernel
> compile and a tools/perf/ compile.

>   "Yo Dawg, I heard you like kernel compiles, so I put a kernel
> compile in your kernel compile so that you can compile the kernel
> while you compile the kernel".

:-)

> But at least the "make install" problem is repeatable, though.

Well, I just tried it, and the only thing that gets rebuilt are the CHK
environment tests that try to figure out what can be built into perf,
i.e. perl, python, libaudit, etc.

Its something that annoys me as well, but not so much as to make me
figure out how to make those be done only if some source file changed.

But then, if you remove, say, libelf from your system so that you get a
perf tool that uses just /proc/kallsyms, it wouldn't detect it...

Perhaps in that case we should say: want a new build with a different
environment? Do a 'make clean' first.

But if I do it as a normal user and then try installing as root... it
behaves like you described, duh :-\

Because of this:

    * new build flags or prefix

Will check...

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