fcoe_ctlr_get_lesb(9)
π fcoe_ctlr_get_lesb(9) β from the Kernel API Manual, bestie π
okay so picture this: you're deep in the kernel, you've got yourself a Fibre Channel over Ethernet situation, and you need the Link Error Status Block β the LESB β for one specific fcoe controller device. That's literally the whole gig. This function is the little hook that grabs it for you. No cap. β¨
πΈ NAME πΈ
fcoe_ctlr_get_lesb β get the Link Error Status Block (LESB) for a given fcoe controller device π¦
β¨ SYNOPSIS β¨
void fcoe_ctlr_get_lesb (struct fcoe_ctlr_device *ctlr_dev );
that's it, that's the whole signature. void, so nothing comes back out β it just does the thing. π
π«Ά ARGUMENTS π«Ά
ctlr_devβ the given fcoe controller device. yes bestie, the one you're asking about. you hand it over and it's like "say less" π
π₯ SEE ALSO π₯
the kernel file that lives at ./drivers/scsi/fcoe/fcoe_transport.c β go look, it's right there π§
and then the whole friend group, in order, no skipping:
fcoe_link_speed_update(9)__fcoe_get_lesb(9)fcoe_get_lesb(9)fcoe_validate_vport_create(9)fcoe_get_wwn(9)fcoe_fc_crc(9)fcoe_start_io(9)fcoe_clean_pending_queue(9)fcoe_check_wait_queue(9)fcoe_queue_timer(9)fcoe_get_paged_crc_eof(9)fcoe_transport_lookup(9)fcoe_transport_attach(9)fcoe_transport_detach(9)fcoe_netdev_map_lookup(9)fcoe_if_to_netdev(9)libfcoe_device_notification(9)fcoe_transport_create(9)fcoe_transport_destroy(9)fcoe_transport_disable(9)fcoe_transport_enable(9)libfcoe_init(9)libfcoe_exit(9)
like, the whole fcoe clique showed up to the party and they all brought their (9) badges π
lowkey the real ones know this page comes out of ./drivers/scsi/fcoe, dated October 2026 β so when you cite it, cite it with your whole chest π
okay that's the page, ily, go read your kernel source π«Άπβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms