fcoe_ctlr_mode_set(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’– fcoe_ctlr_mode_set(9) πŸ’–

okay so bestie, this is fcoe_ctlr_mode_set(9) from the Kernel API Manual. It's short, it's specific, and every detail is doing its little main-character moment. Let's go. 🫢

✨ NAME ✨

fcoe_ctlr_mode_set β€” set or reset the ctlr's mode. That's the whole vibe. πŸ’…

πŸŽ€ SYNOPSIS πŸŽ€

void fcoe_ctlr_mode_set (struct fc_lport *lport , struct fcoe_ctlr *fip
, enum fip_mode fip_mode );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • lport β€” the local port to be (re)configured. literally the local port getting its little refresh. ✨
  • fip β€” the FCoE controller whose mode is changing. it's giving "main character controller." πŸ‘‘
  • fip_mode β€” the new fip mode. the fresh mode in question. πŸ“

🌈 DESCRIPTION 🌈

Okay so here's the note, and it is important, bestie: we shouldn't be changing the libfc discovery settings (fc_disc_config) while an lport is going through the libfc state machine. no cap. 😭

The mode can only be changed when a fcoe_ctlr device is disabled, so that should ensure that this routine is only called when nothing is happening. That's the whole safety vibe check. πŸ’–

tl;dr energy: don't be messing with fc_disc_config mid-libfc-state-machine, and remember the mode-change situation only happens when a fcoe_ctlr device is disabled. periodt. πŸ’…

πŸ‘‘ SEE ALSO πŸ‘‘

Go peek at the kernel file and the whole fcoe cinematic universe, bestie:


okay that's the whole page, bestie. This has been fcoe_ctlr_mode_set(9) β€” source/version: ./drivers/scsi/fcoe, date: October 2026. stay iconic, and don't change modes while things are mid-state-machine, mwah πŸ’‹βœ¨

πŸ“¦ where this page comes from