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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20130715185624.GB1706@redhat.com>
Date:	Mon, 15 Jul 2013 14:56:24 -0400
From:	Dave Jones <davej@...hat.com>
To:	Steven Rostedt <rostedt@...dmis.org>
Cc:	Frederic Weisbecker <fweisbec@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: nohz: Warn if the machine can not perform nohz_full

On Mon, Jul 15, 2013 at 02:49:42PM -0400, Steven Rostedt wrote:
 
 > > And here's a Core Duo from circa 2008.
 > > http://paste.fedoraproject.org/25429/13739098/raw
 > > 
 > > Two for two so far. I get the feeling you guys are going to get a ton of these reports.
 > 
 > Hmm, we should only warn if the user tried to enable nohz-full via the
 > command line. But it looks like it warns even without enabling
 > nohz-full, which wasn't the desired effect.
 > 
 > I'll look at this, and send a patch to make sure the warning only
 > happens when the user tries to use nohz-full, and doesn't just compile
 > it in. The point of the patch is to not let the user think they have
 > nohz-full when they don't.

Is a printk not enough for that purpose ? Tainting the kernel is kinda anti-social.

	Dave

--
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