gss_krb5_mic_build_sg(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ gss_krb5_mic_build_sg(9) πŸŽ€

okay so bestie, this is the gss_krb5_mic_build_sg(9) page from the Kernel API Manual β€” and it's literally Build scatterlist for MIC token operations energy. No cap, let's go πŸ’…


✨ NAME ✨

  • gss_krb5_mic_build_sg β€” Build scatterlist for MIC token operations. That's the whole name, periodt 🫢

πŸ¦‹ SYNOPSIS πŸ¦‹

here's the actual signature, bestie β€” copy it exactly:

int gss_krb5_mic_build_sg (const struct xdr_buf *body , void *cksum ,
       unsigned int cksum_len , void *hdr , struct scatterlist *sg_head ,
       struct scatterlist **sg_overflow );

πŸ’– ARGUMENTS πŸ’–

  • body β€” xdr_buf containing the message body. Main character message body, honestly.
  • cksum β€” pointer to checksum area in the token buffer.
  • cksum_len β€” length of checksum area.
  • hdr β€” pointer to GSS token header.
  • sg_head β€” caller-provided scatterlist array; if more than XDR_BUF_TO_SG_NENTS entries are needed, an overflow scatterlist is allocated and chained automatically. It handles the overflow so you don't have to, slay.
  • sg_overflow β€” OUT: overflow scatterlist, caller must kfree. Don't forget the kfree, bestie β€” that's your job. πŸ™ˆ

πŸ”₯ DESCRIPTION πŸ”₯

okay so per RFC 4121 Section 4.2.4, MIC token checksums cover the message body followed by the token header. The checksum output or received checksum occupies the first scatterlist entry. This layout cannot be constructed by xdr_buf_to_sg_alloc because the checksum area and the GSS header lie outside the xdr_buf.

Returns the number of scatterlist entries on success, or a negative errno on failure. So it either gives you a count or gives you an error β€” vibe check complete. πŸ’…


πŸ‘‘ SEE ALSO πŸ‘‘

Go read these too, iykyk πŸ‘€


mwah πŸ’‹ β€” big kiss from ./net/sunrpc/auth_gss, October 2026, on the gss_krb5_mic_build_sg(9) page. You ate that, fr fr. 🫢✨

πŸ“¦ where this page comes from