STRUCT SCIFIOCTL_FENCE_MARK(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– struct scifioctl_fence_mark(9) πŸ’–

okay bestie, welcome to the Kernel API Manual page for struct scifioctl_fence_mark(9) β€” yes, it’s a whole struct and it has main character energy for exactly one job πŸ‘‘βœ¨


🌸 NAME 🌸

struct scifioctl_fence_mark β€” used for SCIF_FENCE_MARK IOCTL. That’s the name-and-purpose situation, and we’re obsessed 🫢

✨ SYNOPSIS ✨

struct scifioctl_fence_mark {
    __s32 flags;
    __u64 mark;
};

πŸ’… Members πŸ’…

  • flags β€” flags. That’s it. The manpage said flags, and we respect the iconic minimalism πŸ’€βœ¨
  • mark β€” fence handle which is a pointer to a __s32. Literally a pointer to a __s32, no cap πŸŽ€

🌈 SEE ALSO 🌈

  • Kernel file ./include/uapi/linux/scif_ioctl.h β€” the file path, bestie πŸ¦‹
  • struct scif_port_id(9)
  • struct scifioctl_connect(9)
  • struct scifioctl_accept(9)
  • struct scifioctl_msg(9)
  • struct scifioctl_reg(9)
  • struct scifioctl_unreg(9)
  • struct scifioctl_copy(9)
  • struct scifioctl_fence_signal(9)
  • struct scifioctl_node_ids(9)

mwah πŸ’‹ this one comes from ./include/uapi/linux, dated October 2026, and it’s the struct scifioctl_fence_mark(9) page β€” bye bestie, slay your ioctls 🫢🌈

πŸ“¦ where this page comes from