nilfs_bmap_assign(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸŽ€ NAME πŸŽ€

okay so this is the nilfs_bmap_assign(9) page from the Kernel API Manual, and the name is giving exactly this: nilfs_bmap_assign β€” assign a new block number to a block. slay. πŸ’…


✨ SYNOPSIS ✨

bestie, here's the signature, exactly:

int nilfs_bmap_assign (struct nilfs_bmap *bmap , struct buffer_head **bh , unsigned long blocknr , union nilfs_binfo *binfo );

🌸 ARGUMENTS 🌸

  • bmap β€” bmap. That's literally the whole note, bestie; no cap. 🫢
  • bh β€” place to store a pointer to the buffer head to which a block address is assigned (in/out). So it's in/out, iykyk. πŸ’…
  • blocknr β€” block number.
  • binfo β€” block information.

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so nilfs_bmap_assign assigns the block number blocknr to the buffer specified by bh. The block information is stored in the memory pointed to by binfo, and the buffer head may be replaced as a block address is assigned β€” in which case a pointer to the new buffer head is stored in the memory pointed to by bh.

The way this is a whole little swap situation 😭✨


πŸ’œ RETURN πŸ’œ

0 on success, or one of the following negative error codes on failure:

  • -EIO β€” I/O error (including metadata corruption).
  • -ENOMEM β€” Insufficient memory available.

πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./fs/nilfs2/bmap.c β€” and these linked pages, bestie:


mwah πŸ’‹ source/version: ./fs/nilfs2; date: October 2026; page: nilfs_bmap_assign(9). bye bestie, go assign that block number 🫢

πŸ“¦ where this page comes from