From: Dave Jones <davej@redhat.com>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Thomas Gleixner <tglx@linutronix.de>
Subject: futex_wait_setup sleeping while atomic bug.
Date: Thu, 11 Sep 2014 11:10:40 -0400 [thread overview]
Message-ID: <20140911151040.GB3008@redhat.com> (raw)
Hit this overnight on Linus tree from yesterday.
BUG: sleeping function called from invalid context at include/linux/freezer.h:56
in_atomic(): 1, irqs_disabled(): 0, pid: 31948, name: trinity-c121
Preemption disabled at:[<ffffffffb90f2512>] futex_wait_setup+0xb2/0x140
CPU: 0 PID: 31948 Comm: trinity-c121 Not tainted 3.17.0-rc4+ #52
ffffffffb9a52f2a 00000000d3f40479 ffff88008a32fd90 ffffffffb9771ba4
0000000000000000 ffff88008a32fdb8 ffffffffb909f02c ffff88008a32ff58
ffff88008a32ff58 0000000000000010 ffff88008a32fe30 ffffffffb90887bc
Call Trace:
[<ffffffffb9771ba4>] dump_stack+0x4e/0x7a
[<ffffffffb909f02c>] __might_sleep+0x11c/0x1b0
[<ffffffffb90887bc>] get_signal+0x6c/0x720
[<ffffffffb9002577>] do_signal+0x37/0x6f0
[<ffffffffb9126ddb>] ? __acct_update_integrals+0x8b/0x120
[<ffffffffb912728c>] ? acct_account_cputime+0x1c/0x20
[<ffffffffb90ab1ab>] ? account_user_time+0x9b/0xb0
[<ffffffffb9002c8c>] do_notify_resume+0x5c/0xa0
[<ffffffffb977be23>] retint_signal+0x46/0x83
BUG: scheduling while atomic: trinity-c121/31948/0x00000002
Preemption disabled at:[<ffffffffb90f2512>] futex_wait_setup+0xb2/0x140
CPU: 0 PID: 31948 Comm: trinity-c121 Not tainted 3.17.0-rc4+ #52
ffff88024d013740 00000000d3f40479 ffff88008a32fec8 ffffffffb9771ba4
ffff8802403eee00 ffff88008a32fee0 ffffffffb909e725 0000000000000000
ffff88008a32ff60 ffffffffb9774db7 000000000000a000 ffff8802403eee00
Call Trace:
[<ffffffffb9771ba4>] dump_stack+0x4e/0x7a
[<ffffffffb909e725>] __schedule_bug+0x65/0xc0
[<ffffffffb9774db7>] __schedule+0x6a7/0xa70
[<ffffffffb97756ee>] schedule_user+0x2e/0x90
[<ffffffffb977bdc1>] retint_careful+0x12/0x2e
note: trinity-c121[31948] exited with preempt_count 1
next reply other threads:[~2014-09-11 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-11 15:10 Dave Jones [this message]
2014-09-11 21:52 ` futex_wait_setup sleeping while atomic bug Thomas Gleixner
2014-09-11 22:16 ` Darren Hart
2014-09-11 23:53 ` Davidlohr Bueso
2014-09-12 0:07 ` Darren Hart
2014-09-12 8:12 ` Thomas Gleixner
2014-09-12 20:10 ` [tip:locking/urgent] futex: Unlock hb-> lock in futex_wait_requeue_pi() error path tip-bot for Thomas Gleixner
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=20140911151040.GB3008@redhat.com \
--to=davej@redhat.com \
--cc=a.p.zijlstra@chello.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.