linux-kernel - Re: [tip:perf/core] bpf: Fix the build on BPF_SYSCALL= y && !CONFIG_TRACING kernels, make it more configurable

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-next>] [day] [month] [year] [list]

Date:	Thu, 02 Apr 2015 08:43:28 -0700
From:	Alexei Starovoitov <ast@...mgrid.com>
To:	davem@...emloft.net, hpa@...or.com, acme@...hat.com,
	acme@...radead.org, torvalds@...ux-foundation.org,
	rostedt@...dmis.org, akpm@...ux-foundation.org,
	a.p.zijlstra@...llo.nl, mingo@...nel.org,
	linux-kernel@...r.kernel.org, peterz@...radead.org,
	jolsa@...hat.com, daniel@...earbox.net,
	masami.hiramatsu.pt@...achi.com, tglx@...utronix.de,
	namhyung@...nel.org, linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] bpf: Fix the build on BPF_SYSCALL= y && !CONFIG_TRACING
 kernels, make it more configurable

On 4/2/2015 7:30 AM, tip-bot for Ingo Molnar wrote:
> Committer:  Ingo Molnar <mingo@...nel.org>
> CommitDate: Thu, 2 Apr 2015 16:28:06 +0200
>
> bpf: Fix the build on BPF_SYSCALL=y && !CONFIG_TRACING kernels, make it more configurable

Thanks for the fix.
I've tried this combination and it was fine, since whole kernel/trace/
directory is not compiled when !CONFIG_TRACING, but I missed the fact
that CONFIG_RING_BUFFER=y also enables kernel/trace/ which this ia64
.config exploited :( I'll add it to my set of configs.
Thanks again for the fix. It makes dependency clear.

Acked-by: Alexei Starovoitov <ast@...mgrid.com>

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