iscsi_boot_create_target(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

🌸 iscsi_boot_create_target(9) 🌸

okay bestie, gather round, because we're diving into the Kernel API Manual and today's main character is iscsi_boot_create_target πŸ’…


✨ NAME ✨

iscsi_boot_create_target β€” literally just creates a boot target sysfs dir, that's the whole vibe πŸŽ€


πŸ¦‹ SYNOPSIS πŸ¦‹

struct iscsi_boot_kobj * iscsi_boot_create_target (struct iscsi_boot_kset *boot_kset , int index , void *data , ssize_t (*show) (void *data, int type, char *buf) , umode_t (*is_visible) (void *data, int type) , void (*release) (void *data) );

no cap, that's the whole signature, every char exactly as it is πŸ‘‘


πŸ’– ARGUMENTS πŸ’–

  • boot_kset β€” the boot kset, your home base for this whole operation 🏠
  • index β€” the target id, aka which target we're talking about πŸ”’
  • data β€” driver specific data for the target, like its little backpack of custom info πŸŽ’
  • show β€” the attr show function, the one that serves the tea when someone reads the attribute β˜•
  • is_visible β€” the attr visibility function, deciding who gets to see what πŸ‘€
  • release β€” the release function, the cleanup crew 🧹

⚠️ NOTE ⚠️

okay this part is important so listen up 🫢 the boot sysfs lib will free the data passed in for the caller when all refs to the target kobject have been released. so like... don't go freeing that data yourself afterwards, because the lib is gonna do it and it does not want you double-dipping πŸ’€


🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/iscsi_boot_sysfs.c

and the whole friend group:


and that's the page, bestie 🧚 shoutout to ./drivers/scsi for housing all this, dated October 2026, and to iscsi_boot_create_target(9) itself for being the icon it is β€” periodt πŸ’œπŸ”₯

πŸ“¦ where this page comes from