From: Li Zefan <lizf@cn.fujitsu.com>
To: fweisbec@gmail.com
Cc: hpa@zytor.com, linux-kernel@vger.kernel.org,
a.p.zijlstra@chello.nl, tglx@linutronix.de, mingo@elte.hu,
linux-tip-commits@vger.kernel.org
Subject: Re: [tip:sched/core] sched: Pull up the might_sleep() check into cond_resched()
Date: Mon, 20 Jul 2009 14:50:19 +0800 [thread overview]
Message-ID: <4A6413AB.2050807@cn.fujitsu.com> (raw)
In-Reply-To: <tip-613afbf83298efaead05ebcac23d2285609d7160@git.kernel.org>
> Commit-ID: 613afbf83298efaead05ebcac23d2285609d7160
> Gitweb: http://git.kernel.org/tip/613afbf83298efaead05ebcac23d2285609d7160
> Author: Frederic Weisbecker <fweisbec@gmail.com>
> AuthorDate: Thu, 16 Jul 2009 15:44:29 +0200
> Committer: Ingo Molnar <mingo@elte.hu>
> CommitDate: Sat, 18 Jul 2009 15:51:44 +0200
>
> sched: Pull up the might_sleep() check into cond_resched()
>
> might_sleep() is called late-ish in cond_resched(), after the
> need_resched()/preempt enabled/system running tests are
> checked.
>
> It's better to check the sleeps while atomic earlier and not
> depend on some environment datas that reduce the chances to
> detect a problem.
>
> Also define cond_resched_*() helpers as macros, so that the
> FILE/LINE reported in the sleeping while atomic warning
> displays the real origin and not sched.h
>
I guess it's this patch that causes lots of "BUG"
BUG: sleeping function called from invalid context at fs/jbd/commit.c:902
in_atomic(): 0, irqs_disabled(): 0, pid: 64, name: kjournald
INFO: lockdep is turned off.
Pid: 64, comm: kjournald Tainted: GF 2.6.31-rc3-tip #15
Call Trace:
[<c042cbd1>] __might_sleep+0xda/0xdf
[<c053e9f4>] journal_commit_transaction+0xb03/0xc5f
[<c043ecc4>] ? try_to_del_timer_sync+0x48/0x4f
[<c0541394>] kjournald+0xcf/0x1fe
[<c0448998>] ? autoremove_wake_function+0x0/0x34
[<c05412c5>] ? kjournald+0x0/0x1fe
[<c0448708>] kthread+0x6b/0x70
[<c044869d>] ? kthread+0x0/0x70
[<c040364b>] kernel_thread_helper+0x7/0x10
BUG: sleeping function called from invalid context at fs/dcache.c:512
in_atomic(): 0, irqs_disabled(): 0, pid: 2005, name: bash
INFO: lockdep is turned off.
Pid: 2005, comm: bash Tainted: GF 2.6.31-rc3-tip #15
Call Trace:
[<c042cbd1>] __might_sleep+0xda/0xdf
[<c04cae29>] __shrink_dcache_sb+0x208/0x27a
[<c04cb038>] shrink_dcache_parent+0x2c/0xcf
[<c04f8371>] proc_flush_task+0xa7/0x194
[<c0437553>] release_task+0x29/0x3b4
[<c0437fe0>] wait_consider_task+0x702/0xa91
[<c043844d>] do_wait+0xde/0x276
[<c0430f6e>] ? default_wake_function+0x0/0x12
[<c0438672>] sys_wait4+0x8d/0xa6
[<c04a3c65>] ? might_fault+0x85/0x87
[<c04386a3>] sys_waitpid+0x18/0x1a
[<c0402ab8>] sysenter_do_call+0x12/0x36
...
...
> Changes in v2:
>
> - Call __might_sleep() directly instead of might_sleep() which
> may call cond_resched()
>
> - Turn cond_resched() into a macro so that the file:line
> couple reported refers to the caller of cond_resched() and
> not __cond_resched() itself.
>
> Changes in v3:
>
> - Also propagate this __might_sleep() pull up to
> cond_resched_lock() and cond_resched_softirq()
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
> LKML-Reference: <1247725694-6082-6-git-send-email-fweisbec@gmail.com>
> Signed-off-by: Ingo Molnar <mingo@elte.hu>
next prev parent reply other threads:[~2009-07-20 6:52 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 6:28 [PATCH 1/7] sched: Drop the need_resched() loop from cond_resched() Frederic Weisbecker
2009-07-16 6:28 ` [PATCH 2/7] sched: Remove obsolete comment in __cond_resched() Frederic Weisbecker
2009-07-18 14:21 ` [tip:sched/core] " tip-bot for Frederic Weisbecker
2009-07-16 6:28 ` [PATCH 3/7] sched: Cover the CONFIG_DEBUG_SPINLOCK_SLEEP off-case for __might_sleep() Frederic Weisbecker
2009-07-18 14:21 ` [tip:sched/core] " tip-bot for Frederic Weisbecker
2009-07-16 6:28 ` [PATCH 4/7] sched: Add a preempt count base offset to __might_sleep() Frederic Weisbecker
2009-07-16 14:14 ` Peter Zijlstra
2009-07-16 14:34 ` Peter Zijlstra
2009-07-16 14:42 ` Frederic Weisbecker
2009-07-18 14:22 ` [tip:sched/core] " tip-bot for Frederic Weisbecker
2009-07-16 6:28 ` [PATCH 5/7] sched: Remove the CONFIG_PREEMPT_BKL case definition of cond_resched() Frederic Weisbecker
2009-07-18 14:22 ` [tip:sched/core] " tip-bot for Frederic Weisbecker
2009-07-16 6:28 ` [PATCH 6/7 v3] sched: Pull up the might_sleep() check in cond_resched() Frederic Weisbecker
2009-07-18 14:22 ` [tip:sched/core] sched: Pull up the might_sleep() check into cond_resched() tip-bot for Frederic Weisbecker
2009-07-20 6:50 ` Li Zefan [this message]
2009-07-20 8:12 ` Frederic Weisbecker
2009-07-20 8:49 ` Peter Zijlstra
2009-07-20 9:13 ` Frederic Weisbecker
2009-07-20 11:56 ` Ingo Molnar
2009-07-20 11:39 ` Peter Zijlstra
2009-07-22 17:17 ` Frédéric Weisbecker
2009-07-22 17:56 ` Peter Zijlstra
2009-07-16 6:28 ` [PATCH 7/7] sched: Convert the only user of cond_resched_bkl to use cond_resched() Frederic Weisbecker
2009-07-18 14:22 ` [tip:sched/core] " tip-bot for Frederic Weisbecker
2009-07-18 14:21 ` [tip:sched/core] sched: Drop the need_resched() loop from cond_resched() tip-bot for Frederic Weisbecker
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=4A6413AB.2050807@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=a.p.zijlstra@chello.nl \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox