linux-kernel - Re: [GIT PULL] printk: Support for full dynticks mode

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 for Android: free password hash cracker in your pocket

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

Message-ID: <1360027363.5642.67.camel@gandalf.local.home>
Date:	Mon, 04 Feb 2013 20:22:43 -0500
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Ingo Molnar <mingo@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: [GIT PULL] printk: Support for full dynticks mode

On Mon, 2013-02-04 at 17:20 -0800, Andrew Morton wrote:
> On Tue,  5 Feb 2013 01:51:18 +0100
> Frederic Weisbecker <fweisbec@...il.com> wrote:
> 
> >       printk: Wake up klogd using irq_work
> 
> That seems reasonable.
> 
> I'm wondering if we can now remove the printk_sched() special-case. 
> iirc, that was needed because wake_up(klogd) would deadlock when called
> from sched internals.  But now that wakeup is punted to the timer tick,
> perhaps this is now unnecessary?
> 
> (Maybe there were other problems, but the 3ccf3e8306 is poor, and its
> author is unavailable.  There's a lesson there!)

I think we can nuke it with the printk irq work. I'll start looking into
that.

Thanks!

-- Steve


--
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/