Since commit a3c751a50fe6 ("vfs: allow unprivileged whiteout creation"),
privileges are no longer required to create whiteout (0,0) char device.
Use /dev/null instead for EPERM test.
Signed-off-by: Jan Stancek <jstancek@redhat.com>
Acked-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
(cherry picked from commit 13fcfa2d6bdd1fb71c4528b47170e8e8fb3a8a32)
Bug: 159055165
Change-Id: Ib077d04085a7c612455b41ef2c6a27a249945bd7
Signed-off-by: Steve Muckle <smuckle@google.com>
********************************* Tests Suites *********************************
Deleted Added
fs_ext4 uevent
timers
************************************ Tests *************************************
Deleted Added
cve.cve-2017-5669 commands.sysctl02_sh
net.tirpc_tests.tirpc_authdes_seccreate crypto.crypto_user02
net.tirpc_tests.tirpc_authdes_create cve.cve-2017-1000380
numa.move_pages08 cve.cve-2017-16995
numa.Numa-testcases ima.evm_overlay
quickhit.asyncio02 net.ipv6.nft6
quickhit.fstat01 net.ipv6.ip6tables
syscalls.bdflush01 net.tcp_cmds.nft
syscalls.fstat01_64 numa.migrate_pages01
syscalls.move_pages08 numa.numa_testcases
syscalls.lstat03_64 numa.migrate_pages03
syscalls.nanosleep03 numa.migrate_pages02
syscalls.fstat05_64 syscalls.ioprio_set03
syscalls.lstat03 syscalls.ioprio_set02
syscalls.ftruncate02 syscalls.ioprio_set01
syscalls.fstat05 syscalls.futex_cmp_requeue01
syscalls.asyncio02 syscalls.prctl07
syscalls.ftruncate02_64 syscalls.ioprio_get01
syscalls.fstat01 syscalls.leapsec01
syscalls.prctl05
syscalls.prctl08
syscalls.prctl09
syscalls.timer_settime02
syscalls.timer_settime01
syscalls.stat02
syscalls.mbind02
syscalls.prctl06
syscalls.acct02
syscalls.timer_create01
syscalls.timer_create02
syscalls.timer_create03
syscalls.futex_cmp_requeue02
syscalls.set_mempolicy04
syscalls.set_mempolicy03
syscalls.set_mempolicy02
syscalls.set_mempolicy01
syscalls.quotactl06
syscalls.quotactl05
syscalls.mbind04
syscalls.vmsplice03
syscalls.quotactl04
syscalls.accept02
syscalls.pkey01
syscalls.copy_file_range03
syscalls.copy_file_range02
syscalls.preadv203_64
syscalls.bpf_prog01
syscalls.bpf_map01
syscalls.fanotify13
syscalls.mbind03
syscalls.fanotify15
syscalls.fanotify14
syscalls.preadv203
syscalls.stat02_64
syscalls.bpf_prog02
syscalls.prctl04
syscalls.setsockopt04
syscalls.capset03
syscalls.timer_delete01
syscalls.timer_delete02
syscalls.capset04
syscalls.pidfd_send_signal02
syscalls.pidfd_send_signal03
syscalls.bpf_prog03
syscalls.pidfd_send_signal01
tracing.pt_ex_kernel
tracing.pt_disable_branch
tracing.pt_snapshot_trace_basic
tracing.pt_ex_user
Test: VtsKernelLtp on x86 cuttlefish, crosshatch
Bug: 148414662
Bug: 150467619
Signed-off-by: Steve Muckle <smuckle@google.com>
Change-Id: Icd54f931f89974fd15077e53dbad8b2b255df918
This adds missing O_CLOEXEC and O_DIRECTORY on old distros, where it's (in glibc) guarded under __USE_GNU. This was needed on SLES 11 (glibc 2.11). Acked-by: Jan Stancek <jstancek@redhat.com> Signed-off-by: Petr Vorel <pvorel@suse.cz>
Although 32bit powerpc is dead, we still have it in the code. Fixes: b15aafd4f0 Signed-off-by: Petr Vorel <pvorel@suse.cz>
The madvise06 case will fail if merge the linux kernel lts patch on the below: https://lore.kernel.org/linux-mm/20191031221602.9375-1-hannes@cmpxchg.org/ Currently, the drop_caches proc file and sysctl read back the last value written, suggesting this is somehow a stateful setting instead of a one-time command. Make it write-only, like e.g. compact_memory. The commit id of the lts patch is: 204cb79ad42f015312a5bbd7012d09c93d9b46fb Since /proc/sys/vm/drop_caches has been merged in 2006 (2.6.16) it's safe to assume it's present. Signed-off-by: Zou Wei <zou_wei@huawei.com> Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
Now, most linux distributions has VFS capabilities supports, so modifying other process cap is never permitted. This case from old capset02.c. Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com> Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com> Reviewed-by: Cyril Hrubis <chrubis@suse.cz>
It adds a preferred linux capabilities version check like capget02. Also, it adds various cases about EPERM error. Signed-off-by: Yang Xu <xuyang2018.jy@cn.fujitsu.com> Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
Signed-off-by: Feiyu Zhu <zhufy.jy@cn.fujitsu.com> Signed-off-by: Cyril Hrubis <chrubis@suse.cz>
When encryption is not enabled in the kernel e4crypt fails with non-zero exit value. The value is then stored to long via the TEST() macro. The problem is that WEXITSTATUS() does not work with long on big endian s390 on older libc[1][2]. And while this is not our bug, it also does not make sense to misuse the TEST() macro for catching return value from tst_test(). [1] https://sourceware.org/bugzilla/show_bug.cgi?id=19613 [2] https://sourceware.org/git/gitweb.cgi?p=glibc.git;h=b49ab5f4503f36dcbf43f821f817da66b2931fe6 Signed-off-by: Cyril Hrubis <chrubis@suse.cz> Acked-by: Jan Stancek <jstancek@redhat.com>