From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 4/4] mmapstress03: Fix 32bit test on 64bit kernel
Date: Thu, 12 Jan 2017 11:41:25 -0500 (EST) [thread overview]
Message-ID: <374582327.1951599.1484239285415.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170112150550.GA5381@rei.lan>
----- Original Message -----
> From: "Cyril Hrubis" <chrubis@suse.cz>
> To: "Jan Stancek" <jstancek@redhat.com>
> Cc: ltp@lists.linux.it
> Sent: Thursday, 12 January, 2017 4:05:51 PM
> Subject: Re: [LTP] [PATCH 4/4] mmapstress03: Fix 32bit test on 64bit kernel
>
> Hi!
> > > /* Ask for a ridiculously large mmap region at a high address */
> > > - if (mmap((void*) (1UL << (POINTER_SIZE - 1)) - pagesize,
> > > - (size_t) ((1UL << (POINTER_SIZE - 1)) - pagesize),
> > > + if (mmap((void*) (1UL << (kernel_bits - 1)) - pagesize,
> >
> > Since this has same range as below, shouldn't it be also 1ULL?
> > Entire series looks OK to me.
>
> Hmm, that produces warnings in case that sizeof(void) == 4 and with
> 64bit kernel since the value is truncated. I guess that the addres
> should be generated accordingly to the binary and not kernel after all
> because of address space limitations.
>
> Something as (((uintptr_t)1) << ((sizeof(void*)<<3) - 1) - pagesize)
Wouldn't this crash same as original?
On 32 bit, it seems that as soon as mmap touches "stack"
we crash. On 64-bit I'm guessing map area is so high, that
we get rejected immediately with ENOMEM.
Example of lowering size to 1M and targeting stack (32bit on 64bit kernel):
# uname -r
4.8.0-1.el7.test.x86_64
Address Kbytes RSS Dirty Mode Mapping
0000000008048000 56 56 56 r-x-- mmapstress03
0000000008048000 0 0 0 r-x-- mmapstress03
0000000008056000 4 4 4 r---- mmapstress03
0000000008056000 0 0 0 r---- mmapstress03
0000000008057000 4 4 4 rw--- mmapstress03
0000000008057000 0 0 0 rw--- mmapstress03
0000000008058000 12 0 0 rw--- [ anon ]
0000000008058000 0 0 0 rw--- [ anon ]
00000000f7519000 4 4 4 rw--- [ anon ]
00000000f7519000 0 0 0 rw--- [ anon ]
00000000f751a000 1756 920 0 r-x-- libc-2.17.so
00000000f751a000 0 0 0 r-x-- libc-2.17.so
00000000f76d1000 4 0 0 ----- libc-2.17.so
00000000f76d1000 0 0 0 ----- libc-2.17.so
00000000f76d2000 8 8 8 r---- libc-2.17.so
00000000f76d2000 0 0 0 r---- libc-2.17.so
00000000f76d4000 4 4 4 rw--- libc-2.17.so
00000000f76d4000 0 0 0 rw--- libc-2.17.so
00000000f76d5000 12 8 8 rw--- [ anon ]
00000000f76d5000 0 0 0 rw--- [ anon ]
00000000f76e7000 124 120 0 r-x-- ld-2.17.so
00000000f76e7000 0 0 0 r-x-- ld-2.17.so
00000000f7706000 4 4 4 rw--- [ anon ]
00000000f7706000 0 0 0 rw--- [ anon ]
00000000f7707000 4 4 4 r---- ld-2.17.so
00000000f7707000 0 0 0 r---- ld-2.17.so
00000000f7708000 4 4 4 rw--- ld-2.17.so
00000000f7708000 0 0 0 rw--- ld-2.17.so
00000000ff873000 132 8 8 rw--- [ stack ]
00000000ff873000 0 0 0 rw--- [ stack ]
---------------- ------- ------- -------
total kB 2132 1148 108
...
mmap2(0xff800000, 1048576, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_FIXED|MAP_ANONYMOUS, 0, 0) = 0xffffffffff800000
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV +++
Segmentation fault
>
> --
> Cyril Hrubis
> chrubis@suse.cz
>
next prev parent reply other threads:[~2017-01-12 16:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 13:23 [LTP] [PATCH 1/4] lib: Add tst_kernel_bits() Cyril Hrubis
2017-01-12 13:23 ` [LTP] [PATCH 2/4] vma03: Disable the test on 64bit kernel as well Cyril Hrubis
2017-01-12 13:23 ` [LTP] [PATCH 3/4] mmapstress03: Small cleanup Cyril Hrubis
2017-01-12 13:23 ` [LTP] [PATCH 4/4] mmapstress03: Fix 32bit test on 64bit kernel Cyril Hrubis
2017-01-12 14:41 ` Jan Stancek
2017-01-12 15:05 ` Cyril Hrubis
2017-01-12 16:41 ` Jan Stancek [this message]
2017-01-12 17:00 ` Cyril Hrubis
2017-01-12 17:00 ` Jan Stancek
2017-01-12 14:40 ` [LTP] [PATCH 1/4] lib: Add tst_kernel_bits() Jan Stancek
2017-01-12 14:45 ` Cyril Hrubis
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=374582327.1951599.1484239285415.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.