_ctl_check_event_type(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… _ctl_check_event_type β€” Kernel API Manual, bestie edition πŸŽ€

okay so this is _ctl_check_event_type(9) from the kernel API manual, and she is lowkey the bouncer at the door of the event log. let's get into it ✨


🌸 NAME 🌸

_ctl_check_event_type β€” literally determines when an event needs logging, no cap πŸ‘‘


✨ SYNOPSIS ✨

int _ctl_check_event_type (struct MPT3SAS_ADAPTER *ioc , u16 event );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ioc β€” the per adapter object 🫢 (yes, per adapter, she's loyal like that)
  • event β€” the firmware event πŸ’«

πŸ’– DESCRIPTION πŸ’–

so the bitmask in ioc->event_type[] is the whole main character here β€” it indicates which events should be be saved in the driver event_log πŸ““. and this bitmask? it's set by the application. like, the app is the one picking the vibe, not the driver. periodt πŸ’…


🌈 RETURN 🌈

returns 1 when the event should be captured πŸ‘‘, or zero β€” which means no match 😭 fr fr.


🧚 SEE ALSO 🧚

Kernel file ./drivers/scsi/mpt3sas/mpt3sas_ctl.c enum block_state(9), and honestly the whole friend group:

like, that's the entire group chat and they're all iconic πŸ’€πŸ‘‘


and that's the page!! brought to you by ./drivers/scsi/mpt3sas, dated October 2026 β€” mwah, go touch some firmware events bestie πŸ“πŸ’œ

πŸ“¦ where this page comes from