linux-kernel - Re: [PATCH -rt] printk: Don't emit console_cpu_notify() for CPU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.02.1111161547560.4902@ionos>
Date:	Wed, 16 Nov 2011 15:48:11 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	Steven Rostedt <rostedt@...dmis.org>
cc:	Yong Zhang <yong.zhang0@...il.com>,
	LKML <linux-kernel@...r.kernel.org>,
	linux-rt-users <linux-rt-users@...r.kernel.org>
Subject: Re: [PATCH -rt] printk: Don't emit console_cpu_notify() for
 CPU_DYING

On Wed, 16 Nov 2011, Steven Rostedt wrote:

> On Wed, 2011-11-16 at 17:42 +0800, Yong Zhang wrote:
> > Otherwise we will get below warning:
> > 
> > BUG: sleeping function called from invalid context at /build/linux/kernel/rtmutex.c:645
> > in_atomic(): 1, irqs_disabled(): 1, pid: 1054, name: migration/9
> > no locks held by migration/9/1054.
> > irq event stamp: 36
> > hardirqs last  enabled at (35): [<ffffffff815f5b50>] _raw_spin_unlock_irq+0x30/0x70
> > hardirqs last disabled at (36): [<ffffffff810b7eaf>] stop_machine_cpu_stop+0x8f/0x110
> > softirqs last  enabled at (0): [<ffffffff81051b53>] copy_process+0x6d3/0x1640
> > softirqs last disabled at (0): [<          (null)>]           (null)
> > Pid: 1054, comm: migration/9 Not tainted 3.2.0-rc1-rt2-11312-gbf51260-dirty #12
> > Call Trace:
> 
> Thomas, doesn't printk not print to serial in atomic contexts? Or did
> that change?

Not that I know of.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/