linux-kernel - Re: [GIT PULL] kmemcheck updates for -tip

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

Message-ID: <19f34abd0902220906l73751821u3051cda3542b0518@mail.gmail.com>
Date:	Sun, 22 Feb 2009 18:06:32 +0100
From:	Vegard Nossum <vegard.nossum@...il.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Ingo Molnar <mingo@...e.hu>, Pekka Enberg <penberg@...helsinki.fi>,
	linux-kernel@...r.kernel.org
Subject: Re: [GIT PULL] kmemcheck updates for -tip

2009/2/22 Frederic Weisbecker <fweisbec@...il.com>:
> BTW, I just tested kmemcheck (without these fixes pulled) and encountered some
> troubles with the function graph tracer which hangs during the self tests.
> As well as a message from hrtimer which tells its interrupt is too slow.
>
> Well, I'm pulling latest -tip and will see.

Hm, yes. kmemcheck doesn't work well with ftrace -- you'd have to
disable tracing (i.e. removing the -pg option to gcc) for at least the
x86 page fault handler and the kmemcheck code. I had a patch to fix
this a while ago, but it's not very nice to exclude page faults from
ftrace.

I should make it depend on !FTRACE for now to prevent more
head-scratching from others. Thanks for testing!


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036
--
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/