ufs_inode_getblock(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

ufs_inode_getblock(9) πŸ¦‹

okay so bestie, welcome to the Kernel API Manual page for ufs_inode_getblock β€” and it's literally giving β€œallocate new block” energy. no cap, that's the whole NAME vibe. πŸ’…

✨ NAME ✨

ufs_inode_getblock β€” allocate new block 🌸

πŸ¦‹ SYNOPSIS πŸ¦‹

u64 ufs_inode_getblock (struct inode *inode , u64 ind_block , unsigned
       index , sector_t new_fragment , int *err , int *new , struct folio
       *locked_folio );

iconic signature, periodt. ✨

πŸ’… ARGUMENTS πŸ’…

  • inode β€” pointer to inode 🫢
  • ind_block β€” block number of the indirect block
  • index β€” number of pointer within the indirect block
  • new_fragment β€” number of new allocated fragment (block will hold this fragment and also uspi->s_fpb-1) 🌟
  • err β€” see ufs_inode_getfrag
  • new β€” see ufs_inode_getfrag
  • locked_folio β€” see ufs_inode_getfrag

πŸ”₯ SEE ALSO πŸ”₯


that's the whole page, babe πŸŽ€ source/version: ./fs/ufs Β· date: October 2026. mwah πŸ’–

πŸ“¦ where this page comes from