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
| ||
|
Date: Thu, 15 Mar 2012 12:00:39 +0100 From: Peter Zijlstra <a.p.zijlstra@...llo.nl> To: Mandeep Singh Baines <msb@...omium.org> Cc: Andrew Morton <akpm@...ux-foundation.org>, Don Zickus <dzickus@...hat.com>, LKML <linux-kernel@...r.kernel.org>, Michal Hocko <mhocko@...e.cz>, Ingo Molnar <mingo@...e.hu> Subject: Re: [PATCH] watchdog: Make sure the watchdog thread gets CPU on loaded system On Wed, 2012-03-14 at 18:45 -0700, Mandeep Singh Baines wrote: > You could make MAX_RT_PRIO greater than MAX_USER_RT_PRIO but that > might > have some impact on real-time applications. A simple one-line patch: > > - #define MAX_RT_PRIO MAX_USER_RT_PRIO > + #define MAX_RT_PRIO (MAX_USER_RT_PRIO + 1) > > would prevent user-space from causing a false lockup detection. We're so not going to muck with the fifo priorities just for this stupid soft watchdog,.. I already hate that I can't disable the piece of crap, making it more involved is just really not going to happen. -- 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