linux-kernel - Re: [PATCH 0/9] oprofile: port to the new ring buffer

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: <20081216154920.d6b922bb.akpm@linux-foundation.org>
Date:	Tue, 16 Dec 2008 15:49:20 -0800
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Robert Richter <robert.richter@....com>
Cc:	linux-kernel@...r.kernel.org, oprofile-list@...ts.sourceforge.net,
	mingo@...e.hu, rostedt@...dmis.org
Subject: Re: [PATCH 0/9] oprofile: port to the new ring buffer

On Thu, 11 Dec 2008 17:41:54 +0100
Robert Richter <robert.richter@....com> wrote:

> This patch set ports cpu buffers in oprofile to the new ring buffer
> provided by the tracing framework.

alpha allmodconfig:

arch/alpha/oprofile/../../../drivers/oprofile/buffer_sync.c: In function 'sync_buffer':
arch/alpha/oprofile/../../../drivers/oprofile/buffer_sync.c:398: warning: 'offset' may be used uninitialized in this function
make[1]: *** [arch/alpha/oprofile/../../../drivers/oprofile/buffer_sync.o] Error 1                                                    

because stupid gcc thinks that

	lookup_dcookie(mm, s->eip, &offset);

didn't initialise `offset', and arch/alpha is compiled with -Werror.

I'm not sure what to do about that, apart from finding (or building) a
new alpha cross-compiler.

What a PITA.   I do so wish that someone would maintain a suite of
cross-compilers for kernel developers.
--
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/