New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/sys/unix: add memfd_secret systemcall #51547
Comments
In general we don't require a proposal for adding a simple system call to x/sys/unix, and |
My apologies. I thought it fit more than the other issue options
memfd_create is already in x/sys/unix. This issue is about adding memfd_secret |
Sorry, I meant to write |
FYI, until a |
I think @gopherbot is taking the day off. Solved by CL 397774 (golang/sys@b1e9470). |
Hi @ericlagergren , there's no
|
@nadoo thanks, sorry about that. @ianlancetaylor I’ll send a new CL limiting this to just arm64 and amd64 Linux, then. |
@ericlagergren thanks for adding this. Is the right solution here to remove I think that would require a |
We don't require a riscv64 system to regenerate the files. They are generated for all Linux architectures at once as outlined in x/sys/unix/README. If there isn't a |
|
Change https://go.dev/cl/411375 mentions this issue: |
Change https://go.dev/cl/411376 mentions this issue: |
Update to 5.19-rc2 instead of 5.18 for the following reasons: - Support for LoongArch has been merged upstream. This allows to drop the loong64 specific kernel patches. - Fixes [1] an issue encountered with when generating the SOCK_TXREHASH_DEFAULT constant from linux/socket.h on 5.18 - Contains a fix [2] to provide SYS_MEMFD_SECRET on linux/riscv64 as well, The underlying syscall was already available in earlier kernel versions. Also see golang/go#51547. [1] https://lore.kernel.org/r/20220531094345.13801-1-tklauser@distanz.ch [2] https://lore.kernel.org/r/20220505081815.22808-1-tklauser@distanz.ch Change-Id: I6c3ec30a067eae339c443ee55962d94c84feffd9 Reviewed-on: https://go-review.googlesource.com/c/sys/+/411375 Auto-Submit: Tobias Klauser <tobias.klauser@gmail.com> Reviewed-by: Ian Lance Taylor <iant@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Auto-Submit: Ian Lance Taylor <iant@google.com> Run-TryBot: Tobias Klauser <tobias.klauser@gmail.com> Run-TryBot: Ian Lance Taylor <iant@google.com> Reviewed-by: Cherry Mui <cherryyz@google.com>
Linux kernel version 5.14 added the memfd_secret syscall to allow processes to create memory regions that even the kernel itself cannot access. It'd be very useful to have this system-call available in sys/unix.
I see that there's currently a
SYS_MEMFD_SECRET = 447
signal defined here, but I'm not sure how this is related to the system-callThe text was updated successfully, but these errors were encountered: