Date: Tue, 8 Jan 2008 10:17:42 +0100
From: Ingo Molnar <mingo@elte.hu>
To: Kyle McMartin <kyle@mcmartin.ca>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
       Rusty Russell <rusty@rustcorp.com.au>,
       Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] call sysrq_timer_list_show from a workqueue
Message-ID: <20080108091742.GD27671@elte.hu>
References: <20080108063113.GA21287@fattire.cabal.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20080108063113.GA21287@fattire.cabal.ca>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 739
Lines: 23


(Rusty Cc:-ed)

* Kyle McMartin <kyle@mcmartin.ca> wrote:

> handle_sysrq can be called from interrupt context. 
> sysrq_timer_list_show eventually starts poking at module symbols which 
> take the module mutex.
> 
> so instead, let's just kick off a workqueue.
> 
> [ doesn't happen on my laptop with the keyboard, but does when
>   triggered from /proc/sysrq-trigger ]

hmmm. This really shouldnt be happening - how come we hit the module 
mutex on simple things like symbol lookups?

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