From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 797362C00B0 for ; Wed, 5 Sep 2012 05:49:31 +1000 (EST) Message-ID: <1346788157.3025.12.camel@pasglop> Subject: Re: 3.5+: yaboot, Invalid memory access From: Benjamin Herrenschmidt To: Steven Rostedt Date: Wed, 05 Sep 2012 05:49:17 +1000 In-Reply-To: <1346768840.27919.2.camel@gandalf.local.home> References: <1346741491.7619.12.camel@concordia> <1346768840.27919.2.camel@gandalf.local.home> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Cc: Christian Kujau , linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Tue, 2012-09-04 at 10:27 -0400, Steven Rostedt wrote: > As a test case, continuing on error is fine, but I would not recommend > that as a fix. If it fails, but still does the patch, that could be > harmful, and confusing of a result. > > Need to figure out why put_user is failing. It's probably not failiing... it's just called in a context in very early boot on ppc32 where the might_sleep() test in there will trip (because we are running before we are operating at our link address) and will crash horribly. I'll try to figure out a good way to fix this today. Cheers, Ben.