android_kernel_motorola_sm6375/include/uapi
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Saranya R 1e8b9e570d 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>
(cherry picked from commit ab1865af0c)
2023-10-04 10:07:14 -07:00
..
asm-generic Configured process_madvise with upstream syscall number 2023-10-04 10:07:14 -07:00
drm
linux Merge android11-5.4.242+(e699d54) into msm-5.4 2023-07-26 14:21:25 +05:30
media
misc
mtd
rdma
scsi
sound Merge android11-5.4.233+ (4716ccc) into msm-5.4 2023-05-30 11:16:10 +05:30
video
xen
Kbuild