| f6051f894e8829d97486221d5204017b6f7acc56 |
|
12-Jan-2017 |
Cyril Hrubis <chrubis@suse.cz> |
vma03: Disable the test on 64bit kernel as well
The test works only on a 32bit kernel, otherwise we cannot cause the
overflow.
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
Acked-by: Jan Stancek <jstancek@redhat.com>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| 06b5b0d0da3805e801096e9b2b8ffb299d516ed9 |
|
22-Jul-2016 |
Khem Raj <raj.khem@gmail.com> |
vma03: Align pgoffset for page_size > 4K
The mmap2() pgoffset is counted in 4K units and must be page-aligned,
hence we must align it down to page_size/4096 in a case that the system
has page_size > 4K.
Note also that the pgoffset is counted in units of page_size on ia64 but
as the test runs on 32bit platforms only and ia64 is 64-bit only
platform we do not care.
This fixes the test on ppc64 with 64K pagesize
Signed-off-by: Chuang Dong <Chuang.Dong@windriver.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| d6d11d08678aac1ed2c370ea8e42e5f45aea07be |
|
09-Mar-2015 |
Cyril Hrubis <chrubis@suse.cz> |
Introduce tst_parse_opts()
The pattern that was used in all testcases is:
const char *msg;
msg = parse_opts(...);
if (msg)
tst_brkm(TBROK, NULL, "OPTION PARSING ERROR - %s", msg);
This change simplifies the steps to just calling:
tst_parse_opts(...);
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| aabb8340f63ed31afe995fd97795e542dc68b93c |
|
04-Feb-2015 |
Cyril Hrubis <chrubis@suse.cz> |
Include usctest.h in test.h
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| 605fa3362fd7cef0baa2131be32cf44661783d3e |
|
04-Feb-2015 |
Cyril Hrubis <chrubis@suse.cz> |
Get rid of TEST_CLEANUP
Special thanks to Coccinelle for making this easy job.
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| 0b9589f3f9c0345b29cfcf7da5a1253c708303eb |
|
27-May-2014 |
Cyril Hrubis <chrubis@suse.cz> |
testcases: Constify char *msg variable.
The parse_opts() now returns const char * instead of char * this commit
fixes all warnings caused by the change.
Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| c055410d2cc0cb94a017da82f6db3d726870432d |
|
27-May-2013 |
Shuang Qiu <shuang.qiu@oracle.com> |
Unmap the mapped address region
It does not unmap the mapped address region,so we sometimes still get
such
warning when cleanup with nfs as TMPDIR although the file descriptor is
closed:
0 TWARN : tst_rmdir: rmobj(/mnt/nfsv3/ltp-MOeIFH7102/vma4FwRqb)
failed:
unlink(/mnt/nfsv3/ltp-MOeIFH7102/vma4FwRqb/.nfs000000000110cb3600000001)
failed; errno=16: Device or resource busy
Signed-off-by: Shuang Qiu <shuang.qiu@oracle.com>
Reviewed-by: Jan Stancek <jstancek@redhat.com>
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| d59a659cd639ca2780b00049d102acd2a783d585 |
|
07-Mar-2013 |
Caspar Zhang <caspar@casparzhang.com> |
s/Tst_count/tst_count/ to avoid CamelCase
when using latest checkpatch.pl, CamelCase variables are not encouraged,
this patch does a batch update to replace all var `Tst_count` with
`tst_count`.
Signed-off-by: Caspar Zhang <caspar@casparzhang.com>
Acked-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| 354ebb48db8e66a853a58379a4808d5dcd1ceac3 |
|
07-Dec-2012 |
Wanlong Gao <gaowanlong@cn.fujitsu.com> |
cleanup code indent
Cleanup the code indent using:
find . -name *.c -exec Lindent {} \;
It's really a big change, but can fix almost all of
the indent problem in C code, although we can't
ensure all of the changes are right, but the error
changes are really few.
Signed-off-by: Wanlong Gao <gaowanlong@cn.fujitsu.com>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|
| 2b4138a05e90007f2756017378fcc4bcd78e2607 |
|
16-Jan-2012 |
Caspar Zhang <caspar@casparzhang.com> |
mm/vma03: new testcase
vma03 - CVE-2011-2496 avoid wrapping vm_pgoff in mremap()
This is a reproducer for CVE-2011-2496.
The normal mmap paths all avoid creating a mapping where the pgoff
inside the mapping could wrap around due to overflow. However, an
expanding mremap() can take such a non-wrapping mapping and make it
bigger and cause a wrapping condition. There is also another case
where we expand mappings hiding in plain sight: the automatic stack
expansion.
This program tries to remap a mapping with a new size that would
wrap pgoff. Notice that it only works on 32-bit arch for now.
Signed-off-by: Caspar Zhang <caspar@casparzhang.com>
/external/ltp/testcases/kernel/mem/vma/vma03.c
|