fdls_schedul...e_retry_work(9)

💖 fdls_schedule_oxid_free_retry_work(9) 💖

okay so first things first, bestie — this page lives in the Kernel API Manual (yes, the whole thing, it's giving "big kernel energy"). And real talk, the header up top literally prints the name all squished like fdls_schedul...e_retry_work(9) because it's so long it can't even, so don't panic, that's just the man page being dramatic. The full glow-up name is fdls_schedule_oxid_free_retry_work. 🫶

✨ NAME ✨

fdls_schedule_oxid_free_retry_work — the thread that schedules the oxid to be freed later. literally its whole job. no cap. 🎀

🌸 SYNOPSIS 🌸

void fdls_schedule_oxid_free_retry_work (struct work_struct *work );

🦋 ARGUMENTS 🦋

• work — handle to the work struct. that's it, that's the vibe check. ✨

👑 SEE ALSO 👑

okay bestie, here's the whole friend group, they all hang out in the kernel file ./drivers/scsi/fnic/fdls_disc.c:

• fdls_alloc_oxid(9)
• fdls_free_oxid_idx(9)
• fdls_reclaim_oxid_handler(9)
• fdls_free_oxid(9)
• fdls_schedule_oxid_free(9)
• fdls_send_fabric_logo(9)
• fdls_tgt_logout(9)
• fdls_process_fabric_logo_rsp(9)

💅 and that's the whole page, periodt. this masterpiece ships from ./drivers/scsi/fnic and is stamped October 2026 — so yeah, it's from the future, main character energy fr fr. mwah 🍓🧚💜