linux-kernel - Re: [PATCH] sysrq: freeze other CPUs during sysrq-t

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] [day] [month] [year] [list]

Date:	Wed, 20 Aug 2008 19:28:37 -0300
From:	"Gary Shi" <garyu.shi@...il.com>
To:	"Jeremy Fitzhardinge" <jeremy@...p.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] sysrq: freeze other CPUs during sysrq-t

On 8/16/08, Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> Why not use stop_machine()?

Just know about  stop_machine() from your reply. Thanx. But after
checking its src, I feel its too demanding to fit sysrq-t use; e.g.,
when other cpus got deadlocked on some spin locks with preempt
disabled, then the kernel threads of stopmachine won't get a chance to
run on other cpus.

We would expect one or more cpus response only to irqs, when we try to
collect sysrq data; most of the  time, only when the systems hang for
whatever reasons does the sysrq data need to be collected, right?

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