From: Ilya Dryomov <ilya.dryomov@inktank.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
oleg@redhat.com, Linus Torvalds <torvalds@linux-foundation.org>,
tglx@linutronix.de, Mike Galbraith <umgwanakikbuti@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [RFC][PATCH 0/7] nested sleeps, fixes and debug infra
Date: Wed, 6 Aug 2014 11:51:29 +0400 [thread overview]
Message-ID: <CALFYKtAVQ9Rgu_QWCqUkNHk4-wbiVK0FeiwLDttaxZC5bnnG5w@mail.gmail.com> (raw)
In-Reply-To: <20140805130646.GZ19379@twins.programming.kicks-ass.net>
On Tue, Aug 5, 2014 at 5:06 PM, Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, Aug 05, 2014 at 12:33:16PM +0400, Ilya Dryomov wrote:
>> On Mon, Aug 4, 2014 at 2:30 PM, Peter Zijlstra <peterz@infradead.org> wrote:
>> > Hi,
>> >
>> > Ilya recently tripped over a nested sleep which made Ingo suggest we should
>> > have debug checks for that. So I did some, see patch 7. Of course that
>> > triggered a whole bunch of fail the instant I tried to boot my machine.
>> >
>> > With this series I can boot my test box and build a kernel on it, I'm fairly
>> > sure that's far too limited a test to have found all, but its a start.
>>
>> FWIW, I'm getting a lot of these during light rbd testing. CC'ed
>> netdev and linux-mm.
>
> Both are cond_resched() calls, and that's not blocking as such, just a
> preemption point, so lets exclude those.
OK, this one is a bit different.
WARNING: CPU: 1 PID: 1744 at kernel/sched/core.c:7104 __might_sleep+0x58/0x90()
do not call blocking ops when !TASK_RUNNING; state=1 set at
[<ffffffff81070e10>] prepare_to_wait+0x50 /0xa0
Modules linked in:
CPU: 1 PID: 1744 Comm: lt-ceph_test_li Not tainted 3.16.0-vm+ #113
Hardware name: Bochs Bochs, BIOS Bochs 01/01/2007
0000000000001bc0 ffff88006c4479d8 ffffffff8156f455 0000000000000000
ffff88006c447a28 ffff88006c447a18 ffffffff81033357 0000000000000001
0000000000000000 0000000000000950 ffffffff817ee48a ffff88006dba6120
Call Trace:
[<ffffffff8156f455>] dump_stack+0x4f/0x7c
[<ffffffff81033357>] warn_slowpath_common+0x87/0xb0
[<ffffffff81033421>] warn_slowpath_fmt+0x41/0x50
[<ffffffff81078bb2>] ? trace_hardirqs_on_caller+0x182/0x1f0
[<ffffffff81070e10>] ? prepare_to_wait+0x50/0xa0
[<ffffffff81070e10>] ? prepare_to_wait+0x50/0xa0
[<ffffffff8105bc38>] __might_sleep+0x58/0x90
[<ffffffff8148c671>] lock_sock_nested+0x31/0xb0
[<ffffffff8148dfeb>] ? release_sock+0x1bb/0x200
[<ffffffff81498aaa>] sk_stream_wait_memory+0x18a/0x2d0
[<ffffffff810709a0>] ? woken_wake_function+0x10/0x10
[<ffffffff814e058f>] tcp_sendmsg+0xb6f/0xd70
[<ffffffff81509e9f>] inet_sendmsg+0xdf/0x100
[<ffffffff81509dc0>] ? inet_recvmsg+0x100/0x100
[<ffffffff81489f07>] sock_sendmsg+0x67/0x90
[<ffffffff810fe391>] ? might_fault+0x51/0xb0
[<ffffffff8148a252>] ___sys_sendmsg+0x2d2/0x2e0
[<ffffffff811428a0>] ? do_dup2+0xd0/0xd0
[<ffffffff811428a0>] ? do_dup2+0xd0/0xd0
[<ffffffff8105bfe0>] ? finish_task_switch+0x50/0x100
[<ffffffff811429d5>] ? __fget_light+0x45/0x60
[<ffffffff811429fe>] ? __fdget+0xe/0x10
[<ffffffff8148ad14>] __sys_sendmsg+0x44/0x70
[<ffffffff8148ad49>] SyS_sendmsg+0x9/0x10
[<ffffffff815764d2>] system_call_fastpath+0x16/0x1b
Thanks,
Ilya
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-08-06 7:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140804103025.478913141@infradead.org>
2014-08-05 8:33 ` Ilya Dryomov
2014-08-05 13:06 ` Peter Zijlstra
2014-08-06 7:51 ` Ilya Dryomov [this message]
2014-08-06 8:31 ` Peter Zijlstra
2014-08-06 21:16 ` David Miller
2014-08-07 8:10 ` Peter Zijlstra
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=CALFYKtAVQ9Rgu_QWCqUkNHk4-wbiVK0FeiwLDttaxZC5bnnG5w@mail.gmail.com \
--to=ilya.dryomov@inktank.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=umgwanakikbuti@gmail.com \
/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