copy_siginfo_to_external32(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… copy_siginfo_to_external32 πŸ’…

okay so bestie, welcome to the Kernel API Manual page for copy_siginfo_to_external32(9) β€” yes the (9) means it's a kernel-internals kinda situation, we're deep in the kernel section of the manual, buckle up πŸŽ€


✨ NAME ✨

copy_siginfo_to_external32 β€” literally just copying a kernel siginfo into a compat user siginfo. that's the whole vibe. it's giving translation layer πŸ’«


🌸 SYNOPSIS 🌸

void copy_siginfo_to_external32 (struct compat_siginfo *to , const
       struct kernel_siginfo *from );

no cap, that's the signature β€” note the return type is void, so it's not even gonna tell you how it went, it just does the thing 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • to β€” the compat siginfo destination πŸ‘‘ this is where the info is going, the glow-up location, the main character of the copy
  • from β€” the kernel siginfo source πŸ’– this is where the info is coming from, the original, the blueprint

so yeah, from ➑️ to, simple as that, slay πŸ’…


⚠️ NOTE ⚠️

okay this is important, listen up 🧚:

this function does not work properly for the SIGCHLD on x32 β€” but fortunately, it doesn't have to 😌✨

the only valid callers for this function are copy_siginfo_to_user32, which is overriden for x32, and the coredump code. the latter does not care, because SIGCHLD will never cause a coredump πŸ’€ so like, the broken part is safely unreachable, periodt πŸ”₯

fr fr though β€” "doesn't work properly" is a real caveat, don't go inventing new callers and expecting magic to happen πŸ™ˆ

🌈 SEE ALSO 🌈

the kernel file ./kernel/signal.c (iykyk, that's where the lore lives) plus this whole friend group of functions:

that's 26 entries bestie, we listed every single one, no skipping the boring parts in this house πŸ πŸ’–


and that's the page!! this one's from ./kernel, dated October 2026, and it's literally titled copy_siginfo_to_external32(9) β€” k bye, go read signal.c ily πŸ«Άβœ¨πŸŽ€

πŸ“¦ where this page comes from