mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
	buytenh@wantstofly.org, mingo@elte.hu, riku.voipio@movial.fi,
	stable@kernel.org, schwidefsky@de.ibm.com
Subject: Re: + futex-runtime-enable-pi-and-robust-functionality.patch added to -mm tree
Date: Thu, 27 Mar 2008 14:32:19 +1100	[thread overview]
Message-ID: <1206588739.6926.79.camel@pasglop> (raw)
In-Reply-To: <alpine.LFD.1.00.0802161525530.7583@apollo.tec.linutronix.de>


> Hmm, not sure whether there is such code, but then it would be not too bad
> to add
> 
>    if (!p)
>       return -EFAULT;
> 
> to the S390 implementations which only read data and have an exception
> fixup.

I have a different problem on some embedded powerpc's where the TLB miss
code isn't checking for the cached pgdir pointer being NULL (which
happens because we are early at boot and haven't activated an mm). So we
end up either taking recursive faults or going into lalaland walking
the page tables.

It happens on some unreleased code, I'll verify if it happens on
8xx/4xx/etc... in a minute, and will cook a patch if it does.

Cheers,
Ben.


  reply	other threads:[~2008-03-27  3:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200802150149.m1F1n8Gx013909@imap1.linux-foundation.org>
2008-02-16 12:42 ` Heiko Carstens
2008-02-16 13:05   ` Thomas Gleixner
2008-02-16 13:41     ` Heiko Carstens
2008-02-16 13:48       ` Thomas Gleixner
2008-02-16 14:04         ` Heiko Carstens
2008-02-16 14:29           ` Thomas Gleixner
2008-03-27  3:32             ` Benjamin Herrenschmidt [this message]
2008-03-27  3:48               ` Benjamin Herrenschmidt
2008-03-27 12:03                 ` Josh Boyer
2008-02-18 13:00   ` Andrew Morton
2008-02-18 13:10     ` Heiko Carstens
2008-02-18 13:18     ` Heiko Carstens

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=1206588739.6926.79.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=buytenh@wantstofly.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=mm-commits@vger.kernel.org \
    --cc=riku.voipio@movial.fi \
    --cc=schwidefsky@de.ibm.com \
    --cc=stable@kernel.org \
    --cc=tglx@linutronix.de \
    /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

Powered by JetHome