From: Vegard Nossum <vegard.nossum@oracle.com>
To: Rusty Russell <rusty@rustcorp.com.au>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>
Subject: Re: [PATCH] sched/core: add taint on "BUG: sleeping function called from invalid context"
Date: Fri, 29 Jul 2016 08:29:22 +0200 [thread overview]
Message-ID: <579AF7C2.9020009@oracle.com> (raw)
In-Reply-To: <8737mtz1a6.fsf@rustcorp.com.au>
On 07/29/2016 03:22 AM, Rusty Russell wrote:
> Vegard Nossum <vegard.nossum@oracle.com> writes:
>> Seeing this, it occurs to me that we should probably add a taint here:
>
> Taint has traditionally meant "the user did something unsupported, take
> the bug report with a grain of salt". Such as force removing a module.
>
> So this seems wrong...
There are many types of taints. This is the one you mentioned:
2 - A module was force loaded by insmod -f.
This is the one I'd like to set:
512 - A kernel warning has occurred.
(from Documentation/sysctl/kernel.txt).
The flag I want to set is also set on any kind of WARN().
>> BUG: sleeping function called from invalid context at mm/slab.h:388
>> in_atomic(): 0, irqs_disabled(): 0, pid: 32211, name: trinity-c3
>> Preemption disabled at:[<ffffffff811aaa37>] console_unlock+0x2f7/0x930
I am not proposing this patch on a whim: it was actually hiding real
bugs because I only saw an oops that happened later when in fact the
real bug happened where the "sleeping function called from invalid
context" was called.
Vegard
next prev parent reply other threads:[~2016-07-29 6:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-22 19:46 [PATCH] sched/core: add taint on "BUG: sleeping function called from invalid context" Vegard Nossum
2016-07-29 1:22 ` Rusty Russell
2016-07-29 6:29 ` Vegard Nossum [this message]
2016-07-29 13:01 ` Thomas Gleixner
2016-08-10 18:14 ` [tip:sched/core] sched/debug: Add taint on "BUG: Sleeping " tip-bot for Vegard Nossum
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=579AF7C2.9020009@oracle.com \
--to=vegard.nossum@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rusty@rustcorp.com.au \
--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