linux-kernel - Re: [PATCH] nohz: put proper symbol in the unstable schedclock warning

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: <20130830113826.GD7806@somewhere>
Date:	Fri, 30 Aug 2013 13:38:27 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	Steven Rostedt <rostedt@...dmis.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] nohz: put proper symbol in the unstable schedclock
 warning

On Mon, Aug 05, 2013 at 02:21:13PM +0200, Jiri Kosina wrote:
> Since e12d0271 ("nohz: Warn if the machine can not perform nohz_full") 
> Kernel triggers a WARN() in case sched clock is marked as unstable.
> 
> Make it output a proper Kconfig symbol (NO_HZ_FULL) when informing user 
> about this.
> 
> Signed-off-by: Jiri Kosina <jkosina@...e.cz>

I'm queuing this, thanks!

> ---
>  kernel/time/tick-sched.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/kernel/time/tick-sched.c b/kernel/time/tick-sched.c
> index e77edc9..e0030ed 100644
> --- a/kernel/time/tick-sched.c
> +++ b/kernel/time/tick-sched.c
> @@ -182,7 +182,7 @@ static bool can_stop_full_tick(void)
>  		 * Don't allow the user to think they can get
>  		 * full NO_HZ with this machine.
>  		 */
> -		WARN_ONCE(1, "NO_HZ FULL will not work with unstable sched clock");
> +		WARN_ONCE(1, "NO_HZ_FULL will not work with unstable sched clock");
>  		return false;
>  	}
>  #endif
> 
> -- 
> Jiri Kosina
> SUSE Labs
--
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/