__record_default(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– __record_default β€” like, the whole vibe πŸ’–

Okay bestie, so this page is from the Kernel API Manual, section 9, and we're talking about __record_default(9). Buckle up, it's giving "tiny function, huge lore" energy ✨


🌸 NAME 🌸

__record_default β€” it records the default parameters. That's the whole job, and she does it, periodt πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

void __record_default (struct port *port );

πŸŽ€ ARGUMENTS πŸŽ€

  • port β€” the port we're looking at πŸ‘€ like, that's literally it, that's the argument.

✨ DESCRIPTION ✨

So here's what's happening, no cap. This function records the default parameter values for the partner β€” and where does it get those? From the Partner Admin parameters, bestie, that's the source πŸ“₯ β€” and it stamps them in as the current partner operational parameter values.

Then (and this is the slay part) it sets actor_oper_port_state.defaulted to TRUE. βœ…

So yeah: copy the defaults over, flip defaulted to TRUE, done. Iconic behaviour, zero notes 🫢


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/net/bonding/bond_3ad.c β€” the whole friend group lives here, fr fr. Go say hi to:

Like, fifty-seven of them. I counted. That's not a SEE ALSO, that's a whole guest list πŸŽ‰ iykyk.


πŸ’œ That's the whole thing, bestie β€” go forth and be defaulted.

Sign-off szn 🌈 β€” this lil darling ships out of ./drivers/net/bonding, and she's dated October 2026 πŸ—“οΈβœ¨ mwah, take care of her πŸ’‹

πŸ“¦ where this page comes from