apparmor_soc...sock_rcv_skb(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ apparmor_socket_sock_rcv_skb β€” the vibe check before the glow-up ✨

okay bestie, so this is a page from the Kernel API Manual, and the function it's hyping up is literally called apparmor_socket_sock_rcv_skb πŸ’… (the header abbreviates it as apparmor_soc...sock_rcv_skb(9) because apparently even the kernel needs a little nickname sometimes, we've all been there πŸŽ€).


🌸 NAME 🌸

apparmor_socket_sock_rcv_skb β€” it checks perms before associating skb to sk. like, it does the permission vibe check first, no cap. πŸ‘‘


πŸ¦‹ SYNOPSIS πŸ¦‹

int apparmor_socket_sock_rcv_skb (struct sock *sk , struct sk_buff *skb );

that's the whole signature, copy it exactly bestie, don't be weird about it πŸ’–


πŸ’œ ARGUMENTS πŸ’œ

  • sk β€” the sk that you're associating skb with. it's giving "this is where we're gonna attach the thing" ✨
  • skb β€” the skb to check for perms. this one has to pass the vibe check before anything happens πŸ”₯

🫢 NOTE 🫢

⚠️ okay so real talk, this part is important: it can not sleep β€” and it may be called with locks held. so do not go doing sleepy things in here, absolutely not the moment for a nap πŸ’€

also, quoting the page directly: don't want protocol specific in __skb_recv_datagram to deny an incoming connection socket_sock_rcv_skb πŸ™ˆ β€” that's the whole point of this function existing, iykyk.


🌈 SEE ALSO 🌈

okay this is the friend group, and they're all icons honestly πŸŽ€. the kernel file is ./security/apparmor/lsm.c and the whole squad is:

literally the entire lineup, all listed, no skips, we don't do that here πŸ’…βœ¨


🧚 the cute sign-off 🧚

so that's the page! it comes to us from the source path ./security/apparmor, dated October 2026, and the footer repeats the title in its abbrev form apparmor_soc...sock_rcv_skb(9) β€” which, yeah, same energy as a group chat nickname that got cut off mid-word 😭 love that for us. bye bestie, go check those perms! πŸ“πŸ’–πŸŒΊ

πŸ“¦ where this page comes from