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-next>] [day] [month] [year] [list]
Message-ID: <F7F9B0BE3E9BD449B110D0B1CEF6CAEF04FB6F2A@ABGEX01E.abg.fsc.net>
Date:	Wed, 21 Mar 2007 17:06:34 +0100
From:	"Cestonaro, Thilo \(external\)" 
	<Thilo.Cestonaro.external@...itsu-siemens.com>
To:	<linux-kernel@...r.kernel.org>
Subject: how can I touch softlockup watchdog on all cpus?

Hey,

my module generates this ugly softlockup dump, because all cpus are stopped longer then 10 secs.
What I do is:
[code]
local_irq_disable();
// my stuff which takes long and stopps all cpus
.....
touch_softlockup_watchdog();
local_irq_enable();
[/code]

this prevents a dump of my current cpu but not for all.
A call to smp_call_function with a function which calls touch_softlockup_watchdog in it,
doesn't work because smp_call_function needs to be done with irqs enabled, so the watchdog comes first :(.

Any hints or ideas how I can do it in a better way? Disabling softlockup watchdog is not possible for me.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ