Saranya R ab1865af0c Configured process_madvise with upstream syscall number ... 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>		2023-09-24 23:41:02 -07:00
..
boot
configs
include
kernel	Configured process_madvise with upstream syscall number	2023-09-24 23:41:02 -07:00
lib
mm
oprofile
pci
Kconfig
Kconfig.debug
Kconfig.platform
Makefile