linux-kernel - Re: [PATCH][3.10] nohz: Fix lockup on restart from wrong error code

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: <1369160653.6828.151.camel@gandalf.local.home>
Date:	Tue, 21 May 2013 14:24:13 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Peter Zijlstra <peterz@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Paul Gortmaker <paul.gortmaker@...driver.com>,
	Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH][3.10] nohz: Fix lockup on restart from wrong error code

On Tue, 2013-05-21 at 20:12 +0200, Frederic Weisbecker wrote:

> > Signed-off-by: Steven Rostedt <rostedt@...dmis.org>
> 
> There has been this patch that makes it return -EPERM instead:
> https://lkml.org/lkml/2013/5/20/386
> 
> Not sure which is best. Both sort of make sense to me.

That's just as good, as it also fixes the issue.

You can take Li's and add my Acked-by to it. And perhaps even add some
of my change log as well. I believe that will still give the same
problem with reboot, which needs to be fixed.

-- Steve


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