linux-kernel - Re: [PATCH 00/18] tracing/kprobes: Update kprobes with new ftrace changes

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CA+55aFyHntuNYvVhev7+ApoAtX-ywZa-r1m4131qYe8yioG4mw@mail.gmail.com>
Date:	Sun, 12 May 2013 11:56:24 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Steven Rostedt <rostedt@...dmis.org>, Michal Marek <mmarek@...e.cz>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Masami Hiramatsu <masami.hiramatsu.pt@...achi.com>
Subject: Re: [PATCH 00/18] tracing/kprobes: Update kprobes with new ftrace changes

On Sun, May 12, 2013 at 5:50 AM, Steven Rostedt <rostedt@...dmis.org> wrote:
>
> Hmm, I'm still not able to reproduce this. Can you do a make mrproper
> and rebuild and see if you still get that warning.

Hmm. It *may* indicate some kind of build problem. The build I got
that for was an allmodconfig build, but I had interrupted the previous
one in the middle, because I wanted to re-do the build with the proper
version number. I wonder if there's some race where if you ^C the
build at just the right time the CRC's don't get done right?

Michal: any ideas? The errors are of the type:

   WARNING: "ring_buffer_event_data" [*/*/*.ko] has no CRC!

and maybe there's a problem with genksyms.c leaving an empty (or
incomplete) file around when interrupted, and it then gets reused the
next time around?

            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/