fc_queue_devloss_work(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fc_queue_devloss_work β€” bestie, it's the FC devloss workqueue scheduler

okay so this is page fc_queue_devloss_work(9) from the Kernel API Manual, and it's genuinely the most straightforward little function β€” it just puts a piece of work on the fc_host devloss workqueue. no cap, that's the whole vibe. ✨


🌸 NAME 🌸

fc_queue_devloss_work β€” schedule work for the fc_host devloss workqueue.

like. that's it. that's the job. she queues, she slays, she leaves. πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

int fc_queue_devloss_work (struct Scsi_Host *shost , struct fc_rport
*rport , struct delayed_work *work , unsigned long delay );

note the return type is int, bestie β€” that matters, because the return value is literally the whole personality of this function (more on that in DESCRIPTION πŸ‘€).


πŸŽ€ ARGUMENTS πŸŽ€

  • shost β€” pointer to the Scsi_Host that's bound to the fc_host. your entry point, your main character. 🌟
  • rport β€” the rport that this devloss work is associated with. she's the reason we're all here.
  • work β€” the work you want queued for execution. hand her over, she's going on the queue. 🫢
  • delay β€” the jiffies to delay the work queuing by. yes, jiffies. not seconds, not millis β€” jiffies. iykyk ⏳

✨ DESCRIPTION ✨

okay so this is the part where the manpage gets extremely brief and honestly kind of iconic for it. here's the entire description, and i'm quoting the actual facts, not vibing:

Return value: 1 on success / 0 already queued / < 0 for error.

that's the whole thing. no essay, no caveats, just three numbers and a dream. so let's break it down because you deserve the translation:

  • 1 β€” slay, it worked, the work is queued. πŸŽ‰
  • 0 β€” it was already queued, so nothing new happened. not a fail, just a "been there, done that." πŸ’€
  • < 0 β€” error. something went wrong. sad girl hours. 😭
careful with that 0, bestie β€” it does not mean failure here, it means "already queued." don't go treating a zero like a red flag when it's actually just a "we're so back." 🚩➑️🌈

πŸ”₯ SEE ALSO πŸ”₯

the manpage says this lives in the kernel file ./drivers/scsi/scsi_transport_fc.c, and then it drops an absolutely enormous friend group. every single one of these is on the list, no skips, no cuts:

like, that's a whole group chat. fc_queue_devloss_work is literally in the chat with all thirty-two of them. group project energy but make it kernel. πŸ‘‘πŸ’–


and that's the page!! πŸ§šβ€β™€οΈ this little gem lives in ./drivers/scsi, dated October 2026, and it's fc_queue_devloss_work(9) all the way down. mwah πŸ’‹ β€” go queue some work, bestie. πŸŒˆβ­πŸŽ€

πŸ“¦ where this page comes from