linux-kernel - Re: [PATCH] call sysrq_timer_list

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: <20080108091742.GD27671@elte.hu>
Date:	Tue, 8 Jan 2008 10:17:42 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Kyle McMartin <kyle@...artin.ca>
Cc:	linux-kernel@...r.kernel.org, tglx@...utronix.de, mingo@...hat.com,
	Rusty Russell <rusty@...tcorp.com.au>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH] call sysrq_timer_list_show from a workqueue


(Rusty Cc:-ed)

* Kyle McMartin <kyle@...artin.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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/