linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Christian Kujau <lists@nerdbynature.de>, linuxppc-dev@ozlabs.org
Subject: Re: 3.5+: yaboot, Invalid memory access
Date: Wed, 05 Sep 2012 05:49:17 +1000	[thread overview]
Message-ID: <1346788157.3025.12.camel@pasglop> (raw)
In-Reply-To: <1346768840.27919.2.camel@gandalf.local.home>

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.

  reply	other threads:[~2012-09-04 19:49 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-31  5:46 3.5+: yaboot, Invalid memory access Christian Kujau
2012-08-01  2:02 ` Tony Breeds
2012-08-01  7:30   ` Christian Kujau
2012-09-04  6:18 ` Christian Kujau
2012-09-04  6:51   ` Michael Ellerman
2012-09-04  9:32     ` Christian Kujau
2012-09-05  1:08       ` Benjamin Herrenschmidt
2012-09-05  5:25         ` Christian Kujau
2012-09-05  5:29           ` Benjamin Herrenschmidt
2012-09-04 14:27     ` Steven Rostedt
2012-09-04 19:49       ` Benjamin Herrenschmidt [this message]
2012-09-04 19:40     ` Benjamin Herrenschmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1346788157.3025.12.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=lists@nerdbynature.de \
    --cc=rostedt@goodmis.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).