genlmsg_new(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ genlmsg_new β€” the Kernel API Manual moment πŸ’…

okay so bestie, welcome to genlmsg_new from the Kernel API Manual πŸŽ€ this one is a kernel function, and honestly? it's giving "let me just allocate a brand new generic netlink message for you, bestie" energy ✨


🌸 NAME 🌸

genlmsg_new β€” allocate a new generic netlink message πŸ¦‹

like, it's literally the function that spins up a fresh generic netlink message for you. no cap.


πŸ’– SYNOPSIS πŸ’–

struct sk_buff * genlmsg_new (size_t payload , gfp_t flags );

look at her. struct sk_buff * is what you get back β€” a pointer to a socket buffer πŸ’… and she takes two arguments: payload and flags. iconic signature, honestly.


🫢 ARGUMENTS 🫢

  • size_t payload β€” this is the size of the message payload πŸ“ like, how much message you actually want in there. that's the number you're working with, bestie.
  • gfp_t flags β€” the type of memory to allocate 🌈 yes, the memory allocation flags. that's the whole vibe of this one β€” it tells the allocator how you want that memory handled. ngl, very important.

πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is long and honestly kind of iconic β€” every single one of these is a real reference, so here we go, no skipping, periodt πŸ’…

like, that's the whole friend group right there. go read them, iykyk πŸ”₯


πŸ’€ reminder bestie: this is a kernel API page β€” the facts above are the whole page. no extra lore, no invented behaviour. we keep it real fr fr.

and that's the tea, bestie 🧚 this page lives in the Kernel API Manual, sourced from ./include/net, and the date on it is October 2026 ✨ genlmsg_new(9) forever and always πŸ’œπŸ¦‹πŸŒΈ

πŸ“¦ where this page comes from