Changes in Makefile.syscalls

343416f0 - syscalls: fix syscall macros for newfstat/newfstatat

Thu, 01 Aug 2024 12:27:23 +0000

syscalls: fix syscall macros for newfstat/newfstatatThe __NR_newfstat and __NR_newfstatat macros accidentally got renamedin the conversion to the syscall.tbl format, dropping the 'new' portionof the name.In an unrelated change, the two syscalls are no longer architecturespecific but are once more defined on all 64-bit architectures, so the'newstat' ABI keyword can be dropped from the table as a simplification.Fixes: Fixes: 4fe53bf2ba0a ("syscalls: add generic scripts/syscall.tbl")Closes: https://lore.kernel.org/lkml/838053e0-b186-4e9f-9668-9a3384a71f23@app.fastmail.com/T/#tReported-by: Florian Weimer Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/loongarch/kernel/Makefile.syscalls

7697a0fe - LoongArch: Define __ARCH_WANT_NEW_STAT in unistd.h

Sat, 20 Jul 2024 14:40:58 +0000

LoongArch: Define __ARCH_WANT_NEW_STAT in unistd.hChromium sandbox apparently wants to deny statx [1] so it could properlyinspect arguments after the sandboxed process later falls back to fstat.Because there's currently not a "fd-only" version of statx, so that thesandbox has no way to ensure the path argument is empty without beingable to peek into the sandboxed process's memory. For architectures ableto do newfstatat though, glibc falls back to newfstatat after getting-ENOSYS for statx, then the respective SIGSYS handler [2] takes care ofinspecting the path argument, transforming allowed newfstatat's intofstat instead which is allowed and has the same type of return value.But, as LoongArch is the first architecture to not have fstat nornewfstatat, the LoongArch glibc does not attempt falling back at allwhen it gets -ENOSYS for statx -- and you see the problem there!Actually, back when the LoongArch port was under review, people wereaware of the same problem with sandboxing clone3 [3], so clone waseventually kept. Unfortunately it seemed at that time no one had noticedstatx, so besides restoring fstat/newfstatat to LoongArch uapi (andpostponing the problem further), it seems inevitable that we would needto tackle seccomp deep argument inspection.However, this is obviously a decision that shouldn't be taken lightly,so we just restore fstat/newfstatat by defining __ARCH_WANT_NEW_STATin unistd.h. This is the simplest solution for now, and so we hope thecommunity will tackle the long-standing problem of seccomp deep argumentinspection in the future [4][5].Also add "newstat" to syscall_abis_64 in Makefile.syscalls due toupstream asm-generic changes.More infomation please reading this thread [6].[1] https://chromium-review.googlesource.com/c/chromium/src/+/2823150[2] https://chromium.googlesource.com/chromium/src/sandbox/+/c085b51940bd/linux/seccomp-bpf-helpers/sigsys_handlers.cc#355[3] https://lore.kernel.org/linux-arch/20220511211231.GG7074@brightrain.aerifal.cx/[4] https://lwn.net/Articles/799557/[5] https://lpc.events/event/4/contributions/560/attachments/397/640/deep-arg-inspection.pdf[6] https://lore.kernel.org/loongarch/20240226-granit-seilschaft-eccc2433014d@brauner/T/#tCc: stable@vger.kernel.orgSigned-off-by: Huacai Chen List of files: /linux-6.15/arch/loongarch/kernel/Makefile.syscalls

26a3b85b - loongarch: convert to generic syscall table

Tue, 23 Apr 2024 15:41:56 +0000

loongarch: convert to generic syscall tableThe uapi/asm/unistd_64.h and asm/syscall_table_64.h headers can now begenerated from scripts/syscall.tbl, which makes this consistent withthe other architectures that have their own syscall.tbl.Unlike the other architectures using the asm-generic header, loongarchuses none of the deprecated system calls at the moment.Both the user visible side of asm/unistd.h and the internal syscalltable in the kernel should have the same effective contents after this.Signed-off-by: Arnd Bergmann List of files: /linux-6.15/arch/loongarch/kernel/Makefile.syscalls