fc_exch_timer_set_locked(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… fc_exch_timer_set_locked(9) πŸ’…

okay bestie, welcome to the Kernel API Manual page for fc_exch_timer_set_locked(9) β€” yes, the whole page is about starting a timer for an exchange, and it's doing it with the exchange lock held. We love a locked-context moment. πŸ’–

✨ NAME ✨

fc_exch_timer_set_locked β€” Start a timer for an exchange w/ the the exchange lock held. (the double β€œthe” is literally in the original, no cap 😭)

🌸 SYNOPSIS 🌸

void fc_exch_timer_set_locked (struct fc_exch *ep , unsigned int
       timer_msec );

It returns void, so there's no return value to obsess over β€” just timer-starting energy. ⏰✨

πŸŽ€ ARGUMENTS πŸŽ€

  • ep β€” The exchange whose timer will start. That's the main character exchange right there. πŸ‘‘
  • timer_msec β€” The timeout period. The name literally says msec, so you already know the unit vibe. ⏱️

πŸ¦‹ DESCRIPTION πŸ¦‹

This one is used for upper level protocols to time out the exchange. The timer is cancelled when it fires or when the exchange completes. That's the whole vibe: set it, and it goes away when it fires or when the exchange is done. 🫢

And yeah β€” the lock is held, because _locked is right there in the function name and the NAME says β€œw/ the the exchange lock held.” So this is a locked-context situation, periodt. πŸ”’πŸ’…

🌈 SEE ALSO 🌈


okay bestie, that's the whole page! 🫢 Cute little footer sign-off: source/version ./drivers/scsi/libfc, date October 2026, and the page tag fc_exch_timer_set_locked(9). Bye πŸ’…βœ¨

πŸ“¦ where this page comes from