rxrpc_kerne...ct_challenge(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… rxrpc_kernel_reject_challenge πŸ’…

okay bestie, welcome to the Kernel API Manual corner of the group chat ✨ this one's literally called rxrpc_kernel_reject_challenge and it's giving "say it to my face" energy, no cap 🫢


🌸 NAME 🌸

rxrpc_kernel_reject_challenge β€” the glow-up that lets a kernel service reject a challenge πŸ’€βœ¨


πŸŽ€ SYNOPSIS πŸŽ€

int rxrpc_kernel_reject_challenge (struct sk_buff *challenge , u32
abort_code , int error , enum rxrpc_abort_reason why );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • challenge β€” the challenge that's getting rejected, bye bestie πŸ‘‹ it's the struct sk_buff in question.
  • abort_code β€” the abort code you stick into the ABORT packet πŸ”₯ literally what goes in there.
  • error β€” your local error value, iykyk.
  • why β€” an indication as to why. that's it, that's the vibe check πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

so the whole point: this lets a kernel service reject a challenge by aborting the connection β€” but only if it's still in an abortable state, bestie. if it's not abortable anymore, that's just how it is 😭

the error gets returned, which is lowkey iconic because it means you can drop this function straight into a return statement and it just works. main character energy fr fr πŸ‘‘


⭐ RETURN ⭐

the error parameter. that's it. hand it back, periodt πŸ’…


🌈 SEE ALSO 🌈

go read them, they're all slay in their own way 🧚


ngl, this page lives in ./net/rxrpc and it's dated October 2026 β€” putting that in the sign-off because it deserves its moment 🌸✨

and that's the whole page bestie, mwah πŸ’‹ rxrpc_kernel_reject_challenge out πŸ’–πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from