A-Team_Digital_Solutions/android_kernel_motorola_sm6375
Watch
2
0
Fork
You've already forked android_kernel_motorola_sm6375
 0
mirror of https://github.com/BobTheBlinker/android_kernel_motorola_sm6375.git synced 2026-10-24 05:29:04 -04:00
Code Issues Projects Releases Packages Wiki Activity

Configured process_madvise with upstream syscall number

Browse source 
Fixing the syscall mapping which was done wrongly by
'commit f4ed73112f ("mm/madvise: introduce process_madvise()
syscall: an external memory hinting API")' by correcting the syscall
number.

unistd#close_range cts testcase is expecting errno as ENOSYS
because msm-5.4 does not support close_range syscall, but it
receives errno as EINVAL because process_madvise is configured
with 436 which is close_range syscall number which leads to
this cts testcase failure. Hence, configured process_madvise
with proper upstream syscall number to fix this cts failure.

Applications using process_madvise that are built with previous
headers needs to be rebuilt. Otherwise the program would not
work as expected.

Change-Id: If524d109aa1f4072e9ed03d7d9f70cc517fd59dc
Signed-off-by: Saranya R <quic_sarar@quicinc.com>
This commit is contained in:
Saranya R 2023-08-31 16:40:12 +05:30 • committed by Swetha Chikkaboraiah
commit ab1865af0c
18 changed files with 79 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

4
include/uapi/asm-generic/unistd.h
View file

@ -850,11 +850,11 @@ __SYSCALL(__NR_pidfd_open, sys_pidfd_open)
#define __NR_clone3 435
__SYSCALL(__NR_clone3, sys_clone3)
#endif
#define __NR_process_madvise 436
#define __NR_process_madvise 440
__SYSCALL(__NR_process_madvise, sys_process_madvise)
#undef __NR_syscalls
#define __NR_syscalls 437
#define __NR_syscalls 441
/*
* 32 bit systems traditionally used different