From: Fengguang Wu <fengguang.wu@intel.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [signal] WARNING: at kernel/lockdep.c:2623 trace_hardirqs_off_caller()
Date: Mon, 10 Sep 2012 09:23:42 +0800 [thread overview]
Message-ID: <20120910012342.GA28439@localhost> (raw)
In-Reply-To: <20120910011332.GN13973@ZenIV.linux.org.uk>
On Mon, Sep 10, 2012 at 02:13:32AM +0100, Al Viro wrote:
> 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
OK.
> regular way to tell your script that it should be either skipped or
> only build-tested?
The build for the entire branch will be auto skipped if any of its
commits has this line in the changelog:
Dont-Auto-Build
Perhaps we can do a similar
Dont-Auto-Boot
to skip the boot tests.
Or I can simply blacklist any branches matching *experimental* and
skip both build/boot tests for them.
Thanks,
Fengguang
next prev parent reply other threads:[~2012-09-10 1:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 0:47 [signal] BUG: unable to handle kernel NULL pointer dereference at 0000000000000001 Fengguang Wu
2012-09-10 0:54 ` [signal] general protection fault Fengguang Wu
2012-09-10 0:56 ` [signal] divide error Fengguang Wu
2012-09-10 0:59 ` [signal] double fault Fengguang Wu
2012-09-10 1:07 ` [signal] WARNING: at kernel/lockdep.c:2623 trace_hardirqs_off_caller() Fengguang Wu
2012-09-10 1:13 ` Al Viro
2012-09-10 1:23 ` Fengguang Wu [this message]
2012-09-10 1:10 ` [signal] BUG: unable to handle kernel NULL pointer dereference at 0000000000000001 Al Viro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120910012342.GA28439@localhost \
--to=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.