[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <19f34abd0806230402x502eca3cna927eb8742553570@mail.gmail.com>
Date: Mon, 23 Jun 2008 13:02:29 +0200
From: "Vegard Nossum" <vegard.nossum@...il.com>
To: "Stephen Rothwell" <sfr@...b.auug.org.au>,
"Steven Rostedt" <srostedt@...hat.com>
Cc: linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
"Pekka Enberg" <penberg@...helsinki.fi>,
"Christoph Lameter" <clameter@....com>
Subject: Re: linux-next: Tree for June 23
On Mon, Jun 23, 2008 at 12:26 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
> On Mon, Jun 23, 2008 at 12:23 PM, Vegard Nossum <vegard.nossum@...il.com> wrote:
>> Testing tracer sched_switch: PASSED
>> Testing tracer sysprof: PASSED
>> Testing tracer ftrace: PASSED
>> Testing dynamic ftrace: PASSED
>> Testing tracer irqsoff: PASSED
>> Testing tracer preemptoff: PASSED
>> Testing tracer preemptirqsoff: <4>------------[ cut here ]------------
>> WARNING: at kernel/lockdep.c:2680 check_flags+0x142/0x160()
>> Pid: 2, comm: kthreadd Not tainted 2.6.26-rc6-next-20080620 #34
>
> <-- Oops, wrong version :-(
>
> Will try the latest one as well.
Okay, I can confirm that this happens with today's tree too. I also
get this (new) warning:
mm/slub.c: In function 'kmem_cache_defrag':
mm/slub.c:3046: warning: 'reclaimed' may be used uninitialized in this function
Otherwise things seem to work good :-)
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/
Powered by blists - more mailing lists