| 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
| ||
|
Message-ID: <20141106055357.530e1458@kryten>
Date: Thu, 6 Nov 2014 05:53:57 +1100
From: Anton Blanchard <anton@...ba.org>
To: Don Zickus <dzickus@...hat.com>
Cc: uobergfe@...hat.com, drjones@...hat.com, akpm@...ux-foundation.org,
linux-kernel@...r.kernel.org, Michael Ellerman <mpe@...erman.id.au>
Subject: Re: Confusing behaviour with /proc/sys/kernel/nmi_watchdog
Hi Don,
> > commit 9919e39a1738 ("kvm: ensure hard lockup detection is disabled
> > by default") provided a way for the kernel to disable the hard
> > lockup detector at runtime.
> >
> > I'm using it on ppc64 but notice some weird behaviour with the
> > nmi_watchdog procfs variable. At boot, that the hard lockup
> > detector appears to be enabled even when we disable it via
> > watchdog_enable_hardlockup_detector(false):
> >
> > # cat /proc/sys/kernel/nmi_watchdog
> > 1
> >
> > I have to echo 0 to it then echo 1 again to enable it.
>
> I believe Andrew answered the question for you, it's a WIP and we have
> patches to clean that up.
Thanks, yes good to see it being worked on.
> I don't see ppc64 watchdog support in arch/powerpc, is that something
> you are working with on implementing?
I've submitted it over on linuxppc-dev:
http://patchwork.ozlabs.org/patch/406802/
Anton
--
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