lpfc_debugfs_disc_trc_data(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_debugfs_disc_trc_data — from the Kernel API Manual, bestie

okay so real talk, this one is a kernel function called lpfc_debugfs_disc_trc_data and it lives in the Kernel API Manual, and it is literally the discovery-log dumper. no cap. let's get into it 🫶

✨ NAME ✨

lpfc_debugfs_disc_trc_data — Dump discovery logging to a buffer 💖

🌸 SYNOPSIS 🌸

int lpfc_debugfs_disc_trc_data (struct lpfc_vport *vport , char *buf ,
int size );

like, that's the whole signature, she's not complicated 💅

🎀 ARGUMENTS 🎀

  • vport — the vport you're pulling the log info out of. she's the source of truth here 👑
  • buf — the buffer where the log gets dumped. yep, we're pouring it in there 🍓
  • size — the maximum amount of data to process. like a hard limit, don't @ me 💀

🦋 DESCRIPTION 🦋

So this routine gathers the lpfc discovery debugfs data from the vport and dumps it to buf, up to size number of bytes. That's the vibe check ✅

The way it works is genuinely kind of iconic: it starts at the next entry in the log and processes the log until the end of the buffer. Then it loops back around and gathers from the beginning of the log, processing until it hits the current entry. so it's like a little wrap-around moment, main character energy 🌈

🔥 NOTES 🔥

okay bestie, important: discovery logging will be disabled while this routine dumps the log. (yes, the original says "while while" — we love her anyway 🙈)

Return Value: this routine returns the amount of bytes that were dumped into buf, and it will not exceed size. so like, no overflow shenanigans, she stays in her lane ✨

⭐ SEE ALSO ⭐

Kernel file ./drivers/scsi/lpfc/lpfc_debugfs.c — go read the source, iykyk 🧚

and then the whole friend group, fr fr:

and that's the page, bestie!! 🎀 this one's from ./drivers/scsi/lpfc, Kernel API Manual, dated October 2026, and it's titled lpfc_debugfs_disc_trc_data(9) — slay, go read your logs 💜✨

📦 where this page comes from