From: Al Viro <viro@ZenIV.linux.org.uk>
To: Fengguang Wu <fengguang.wu@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [signal:execve2] BUG: sleeping function called from sys_brk
Date: Fri, 3 Aug 2012 11:03:06 +0100 [thread overview]
Message-ID: <20120803100305.GC23464@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20120803093028.GA16195@localhost>
On Fri, Aug 03, 2012 at 05:30:28PM +0800, Fengguang Wu wrote:
> Hi Al,
>
> > I got a boot warning on commit
> >
> > tree: git://git.kernel.org/pub/scm/linux/kernel/git/viro/signal.git execve2
> > head: 1ade99215ed3c334a544b9e1773602ff0f0251ab
> > commit: 1ade99215ed3c334a544b9e1773602ff0f0251ab [9/9] x86: switch to generic sys_execve and kernel_execve
>
> The same commit triggers other warnings (new config and dmesg attached):
>
> [ 18.315125] debug: unmapping init [mem 0x816b6000-0x81852fff]
> [ 18.318178] BUG: sleeping function called from invalid context at /c/kernel-tests/src/stable/kernel/rwsem.c:47
> [ 18.318243] in_atomic(): 0, irqs_disabled(): 1, pid: 1, name: init
> [ 18.318243] no locks held by init/1.
> [ 18.318243] Pid: 1, comm: init Not tainted 3.5.0-01258-g1ade992 #182
> [ 18.318243] Call Trace:
> [ 18.318243] [<8109e07d>] __might_sleep+0x13d/0x170
> [ 18.318243] [<813cea7c>] down_write+0x2c/0xd0
> [ 18.318243] [<81166ae9>] sys_brk+0x29/0x1f0
> [ 18.318243] [<813d22d0>] syscall_call+0x7/0xb
Ow... I think I understand what happened here, and I really don't like the
picture ;-/ Could you check if slapping regs->flags = X86_EFLAGS_IF;
in process_32.c:start__thread() gets rid of that?
prev parent reply other threads:[~2012-08-03 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 5:14 [signal:execve2] WARNING at smp_call_function_many() Fengguang Wu
2012-08-03 9:30 ` [signal:execve2] BUG: sleeping function called from sys_brk Fengguang Wu
2012-08-03 10:03 ` Al Viro [this message]
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=20120803100305.GC23464@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox