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 15:29:07 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.1.00.0802161525530.7583@apollo.tec.linutronix.de> (raw)
In-Reply-To: <20080216140444.GC4900@osiris.boeblingen.de.ibm.com>

On Sat, 16 Feb 2008, Heiko Carstens wrote:

> On Sat, Feb 16, 2008 at 02:48:17PM +0100, Thomas Gleixner wrote:
> > 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.
> 
> To be more precise: dereferencing alone won't cause an exception for
> NULL pointers on s390. Only writes will do so.
> That is very architecture specific since we cannot unmap page 0,
> it contains per-cpu data -- like exception pointers and all such stuff
> that the cpu needs.
> Just in case there is any code that relies on the fact that also reads
> via a NULL pointer are supposed to failed.

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.

Thanks,

	tglx

  reply	other threads:[~2008-02-16 14:30 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 [this message]
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.0802161525530.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®