linux-kernel - Re: [signal] WARNING: at kernel/lockdep.c:2623 trace_hardirqs_off

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: <20120910011332.GN13973@ZenIV.linux.org.uk>
Date:	Mon, 10 Sep 2012 02:13:32 +0100
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [signal] WARNING: at kernel/lockdep.c:2623
 trace_hardirqs_off_caller()

On Mon, Sep 10, 2012 at 09:07:07AM +0800, Fengguang Wu wrote:
> Not sure if it's an unrelated warning, but anyway.
> 
> commit: c2865bb326476f031ce7121e876c656cdc12c894 [13/18] x86, um/x86: switch to generic sys_execve and kernel_execve

[commit in experimental-kernel_thread, not one in execve2/for-next/master]

Again, experimental-kernel_thread is build-only for now.  Is there any
regular way to tell your script that it should be either skipped or
only build-tested?
--
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/