public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Kang Kai <Kai.Kang@windriver.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] Posix test case mmap/31-1 fails on Linux/eglibc
Date: Wed, 28 Dec 2011 18:55:55 +0800	[thread overview]
Message-ID: <4EFAF5BB.2030407@windriver.com> (raw)

Hi all,

I run mmap/31-1 failed with ENOMEM on linux, with error message:
off: fffffffffffff000, len: fffffffffffff000
Test FAIL: expect EOVERFLOW but get other error: Cannot allocate memory

But compare to mmap/24-2, it mmap() the same length but pass. Its output:
available memory: 18446744073709551615
addr: 7f78c54fa000, len: ffffffffffffffff
addr: 7f78c54fa000, len: fffffffffffff000
Test Pass: mmap/24-2.c Get ENOMEM: Cannot allocate memory

So I suppose that mmap/31-1 may need update, but I don't know how to 
make mmap() overflow as expect.
Any suggestion is appreciated.

Regards,
Kai

------------------------------------------------------------------------------
Write once. Port to many.
Get the SDK and tools to simplify cross-platform app development. Create 
new or port existing apps to sell to consumers worldwide. Explore the 
Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
http://p.sf.net/sfu/intel-appdev
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

             reply	other threads:[~2011-12-28 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-28 10:55 Kang Kai [this message]
2011-12-28 18:16 ` [LTP] Posix test case mmap/31-1 fails on Linux/eglibc Cyril Hrubis
2012-01-04  1:37 ` Yasuaki Ishimatsu
2012-01-04  2:05   ` Wanlong Gao
2012-01-04  2:50     ` Yasuaki Ishimatsu
2012-01-04  2:57       ` Wanlong Gao
2012-01-04  3:32         ` Kang Kai

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=4EFAF5BB.2030407@windriver.com \
    --to=kai.kang@windriver.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