lpfc_oas_tgt_store(9)

📦 version 7.3.1, in nixpkgs unstable

💅 lpfc_oas_tgt_store(9) — the Kernel API Manual moment ✨

okay so bestie, we're in the Kernel API Manual and today's main character is lpfc_oas_tgt_store(9). yes it's a mouthful, yes it's iconic, no we are not skipping any of it 🎀

✨ NAME ✨

lpfc_oas_tgt_store — stores the wwpn</> of a target whose luns maybe enabled for Optimized Access Storage (OAS) operations. that's the whole vibe. storing a target's wwpn so its luns can maybe get OAS-enabled 💫

🌸 SYNOPSIS 🌸

ssize_t lpfc_oas_tgt_store (struct device *dev , struct device_attribute
*attr , const char *buf , size_t count );

like, look at her. four args. flawless. no cap 🫶

🦋 ARGUMENTS 🦋

  • dev — the class device, which gets converted into a Scsi_host. glow-up via conversion, honestly.
  • attr — the device attribute. and... yeah, it's not used. she's just there for the vibes 💀
  • buf — the buffer where the info gets passed in. that's the payload, bestie 🍓
  • count — size of that data buffer. gotta know how much we're working with, periodt.

👑 RETURN 👑

  • -EINVAL — when count is invalid, or when the wwpn byte is invalid. two separate red flags, same energy 🙈
  • -EPERM — OAS is not supported by hba. she said no and meant it.
  • value of count — on success. slay 💖

⭐ SEE ALSO ⭐

the kernel file is ./drivers/scsi/lpfc/lpfc_attr.c, and here's the whole friend group — literally the entire roster, every single one, no one left out 💜:

bestie heads up: if count is invalid or the wwpn byte is invalid you get -EINVAL, and if the hba doesn't support OAS you get -EPERM. no soft-launching here, she tells you straight 💀

okay that's the page, go be great, iykyk 🧚

💖 that's the whole thing, written in ./drivers/scsi/lpfc, dated October 2026 — like, future queen behaviour. mwah, love u, bye 🎀

📦 where this page comes from