nilfs_ioctl_wrap_copy(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ¦‹ nilfs_ioctl_wrap_copy(9) β€” Kernel API Manual, but make it cute ✨

okay bestie, welcome to the nilfs_ioctl_wrap_copy(9) page β€” yes, that's the manual-name-and-section situation, and we're gonna get through it together πŸ’–

🌸 NAME 🌸

nilfs_ioctl_wrap_copy β€” wrapping function of get/set metadata info. short, sweet, iconic.


πŸŽ€ SYNOPSIS πŸŽ€

int nilfs_ioctl_wrap_copy (struct the_nilfs *nilfs , struct nilfs_argv
       *argv , int dir , ssize_t (*dofunc)(struct the_nilfs *, __u64 *, int,
       void *, size_t, size_t) );

πŸ’… ARGUMENTS πŸ’…

these are the four besties in the function call, no cap:

  • nilfs β€” the nilfs object. main character energy.
  • argv β€” vector of arguments from userspace. literally the receipts from userspace.
  • dir β€” set of direction flags. yeah, direction flags.
  • dofunc β€” concrete function of get/set metadata info. the actual worker bee 🐝

✨ DESCRIPTION ✨

nilfs_ioctl_wrap_copy gets/sets metadata info by means of calling the dofunc function on the basis of the argv argument. if it's successful, the requested metadata information is copied to userspace memory. that's the whole plot, highkey.


πŸ”₯ RETURN πŸ”₯

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

  • -EFAULT β€” Failure during execution of requested operation.
  • -EINVAL β€” Invalid arguments from userspace.
  • -ENOMEM β€” Insufficient memory available.
bestie, those are negative error codes β€” so if you see one, it's not slay, it's a fail. 😭

πŸ¦‹ SEE ALSO πŸ¦‹

Kernel file ./fs/nilfs2/ioctl.c β€” and the whole linked-up friend group:


okay love you, bye! πŸ’– source/version: ./fs/nilfs2 Β· date: October 2026 Β· page: nilfs_ioctl_wrap_copy(9)

πŸ“¦ where this page comes from