linux-kernel - regression from softlockup fix

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: <20071119.012119.118043374.davem@davemloft.net>
Date:	Mon, 19 Nov 2007 01:21:19 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	linux-kernel@...r.kernel.org
CC:	mingo@...e.hu, jeremy@...p.org, gregkh@...e.de
Subject: regression from softlockup fix

This changeset:

commit 436e61d93605a3a36902c9ee510b0ecba0d7d361
Author: Ingo Molnar <mingo@...e.hu>
Date:   Tue Oct 16 23:18:38 2007 -0700

    fix the softlockup watchdog to actually work
 ...

Causes my SMP niagara systems to trigger the softlockup message
frequently when the nohz timer fires.

The backtrace is always in the timer handler, the cpu is not
wedged at all, which makes me think it's likely triggering
erroneously.

I suspect that what is happening is that the NOHZ period is
longer than the softlockup timeout (10 seconds) and we get
an interrupt before the watchdog thread gets onto the cpu.

I'll happily test any suggested fix for this bug, thanks!
-
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/