xbc_node_compose_key_after(9)

📦 version 7.3.1, in nixpkgs unstable

💖 NAME 💖

okay so bestie, welcome to the xbc_node_compose_key_after(9) page from the Kernel API Manual — she's here to explain the whole XBC-node-key-composing situation, and yes, she ate. The official NAME tea is:

  • xbc_node_compose_key_after — Compose partial key string of the XBC node

✨ SYNOPSIS ✨

like, the signature is literally:

       int xbc_node_compose_key_after (struct xbc_node *root , struct xbc_node
       *node , char *buf , size_t size );

🎀 ARGUMENTS 🎀

  • root — Root XBC node. the starting-point girlie for the partial key
  • node — Target XBC node.
  • buf — A buffer to store the key.
  • size — The size of the buf.

🦋 DESCRIPTION 🦋

okay so the actual vibe: compose the partial key of the node into buf, and that partial key starts right after root — and bestie, root is not included. If root is NULL, this returns full key words of node. The return value is the total length of the key stored in buf.

now the error girlies, because we respect them:

  • It returns -EINVAL if node is NULL, or if root is not the ancestor of node, or if root is node.
  • It returns -ERANGE if the key depth is deeper than max depth.

This is expected to be used with xbc_find_node to list up all (child) keys under given key. iykyk — that's the whole point, bestie.

🌈 SEE ALSO 🌈

Kernel file ./lib/bootconfig.c is right there, and the whole friend group is:

mwah 💋 — source path ./lib, date October 2026, page xbc_node_compose_key_after(9) — bye bestie 🫶✨

📦 where this page comes from