mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: 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: Sat, 16 Feb 2008 14:48:17 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802161444510.7583@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080216134155.GB4900@osiris.boeblingen.de.ibm.com>

On Sat, 16 Feb 2008, Heiko Carstens wrote:

> > Well, NULL pointer dereferencing is supposed to fail, isn't it ?
>
> I wasn't sure that this is true for all architectures, but...

It's an requirement for futex support.

> > > Indeed it does fail with an Oops on s390 since we enable low address
> > > protection in the kernel so we get an exception if something within the
> > > kernel writes to the first 512 bytes of the kernel address space.
> > > Otherwise it would have silently passed the test...
> > 
> > NULL pointer dereferencing faults on all architectures, at least it
> > should, but we explicitely disable pagefaults and recover via the
> > extable fixup, which is in S390 as well. That returns -EFAULT and
> > signals that there is a working implementation, while those which have
> > no support return -ENOSYS, which keeps the robust/pi stuff disabled.
> 
> ...one of our exception table entries has an off-by-one bug.
> Never mind, I'll go and fix our own stuff instead ;)

Maybe we should do such tests on all exception table protected
assembler constructs :)

Thanks,

	tglx

  reply	other threads:[~2008-02-16 13:48 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 [this message]
2008-02-16 14:04         ` Heiko Carstens
2008-02-16 14:29           ` Thomas Gleixner
2008-03-27  3:32             ` Benjamin Herrenschmidt
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=alpine.LFD.1.00.0802161444510.7583@apollo.tec.linutronix.de \
    --to=tglx@linutronix.de \
    --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 \
    /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

all inboxes | Powered by JetHome®