public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: chrubis@suse.cz
To: Jan Stancek <jstancek@redhat.com>
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Unifying syscalls tests for EFAULT
Date: Wed, 30 Apr 2014 15:01:05 +0200	[thread overview]
Message-ID: <20140430130105.GA22265@rei> (raw)
In-Reply-To: <1372990689.12607095.1398862329568.JavaMail.zimbra@redhat.com>

Hi!
> > * Is there a machine that has userspace address mapped on NULL ?
> 
> I do recall a testcase, which had special setup for ia64, because
> it didn't work as expected for NULL. When looking at process map,
> there was a single page mapped 0, which didn't come from test:
> 
> # cat /proc/self/maps
> 00000000-00004000 r--p 00000000 00:00 0
> 
> See this email thread:
>   https://www.mail-archive.com/ltp-list@lists.sourceforge.net/msg17855.html

Hmm, so I guess that only portable way to cause EFAULT would be mapping
PROT_NONE page.

-- 
Cyril Hrubis
chrubis@suse.cz

------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
unparalleled scalability from the best Selenium testing platform available.
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  parent reply	other threads:[~2014-04-30 13:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-30 12:14 [LTP] Unifying syscalls tests for EFAULT chrubis
     [not found] ` <1372990689.12607095.1398862329568.JavaMail.zimbra@redhat.com>
2014-04-30 13:01   ` chrubis [this message]
2014-04-30 13:13     ` chrubis

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=20140430130105.GA22265@rei \
    --to=chrubis@suse.cz \
    --cc=jstancek@redhat.com \
    --cc=ltp-list@lists.sourceforge.net \
    /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