linux-kernel - Re: [PATCH] softlock: fix false panic which can occur if softlockup

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

Message-ID: <20090114104826.GF2913@elte.hu>
Date:	Wed, 14 Jan 2009 11:48:26 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Mandeep Singh Baines <msb@...gle.com>
Cc:	linux-kernel@...r.kernel.org, rientjes@...gle.com,
	mbligh@...gle.com, thockin@...gle.com
Subject: Re: [PATCH] softlock: fix false panic which can occur if
	softlockup_thresh is reduced


* Mandeep Singh Baines <msb@...gle.com> wrote:

> At run-time, if softlockup_thresh is changed to a much lower value,
> touch_timestamp is likely to be much older than the new softlock_thresh.
> 
> This will cause a false softlockup to be detected. If softlockup_panic
> is enabled, the system will panic.
> 
> The fix is to touch all watchdogs before changing softlockup_thresh.
> 
> Signed-off-by: Mandeep Singh Baines <msb@...gle.com>
> ---
>  include/linux/sched.h |    3 +++
>  kernel/softlockup.c   |    9 +++++++++
>  kernel/sysctl.c       |    2 +-
>  3 files changed, 13 insertions(+), 1 deletions(-)

applied to tip/core/urgent, thanks!

	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/