mpt3sas_conf...olume_handle(9)
π mpt3sas_config_get_volume_handle β Kernel API Manual, section 9 π
okay so bestie, welcome to the Kernel API Manual β¨ this one's section 9, and we're getting into mpt3sas config land β the part of the kernel that talks to those LSI/Broadcom SAS host bus adapters. pull up a chair, this one's short but it's important, no cap π«Ά
πΈ NAME πΈ
mpt3sas_config_get_volume_handle β returns the volume handle for hidden raid components π
like, you've got these RAID volumes hiding their pieces from you and this function goes "bestie, i got you, here's the handle" π₯
β¨ SYNOPSIS β¨
int mpt3sas_config_get_volume_handle (struct MPT3SAS_ADAPTER *ioc , u16
pd_handle , u16 *volume_handle );
π¦ ARGUMENTS π¦
iocβ the per adapter object. this is your main character π the MPT3SAS adapter you're working with, like, the whole personality of the card honestlypd_handleβ the phys disk handle. that's your input, the physical disk you're asking about πvolume_handleβ the volume handle. this is where the answer goes, it's a pointer so the function can write the volume handle back out to you π«
π CONTEXT π
sleep.
that's it, that's the whole context. it sleeps π΄ which means, bestie, do not call this from an atomic context, no interrupts, no spinlocks-held situations, none of that. it's giving "i need a nap" energy and you have to respect it π
π RETURN π
0 for success, non-zero for failure. slay β¨ literally just vibe-check the return value β zero means we ate, anything else means it didn't work out π
π SEE ALSO π
here's the whole friend group, i'm not leaving a single one out because they'd all notice π
- the kernel file
./drivers/scsi/mpt3sas/mpt3sas_config.c struct config_request(9)_config_display_some_debug(9)_config_alloc_config_dma_memory(9)_config_free_config_dma_memory(9)mpt3sas_config_done(9)_config_request(9)mpt3sas_config_get_manufacturing_pg0(9)mpt3sas_config_get_manufacturing_pg1(9)mpt3sas_config_get_manufacturing_pg10(9)mpt3sas_config_get_manufacturing_pg11(9)mpt3sas_config_set_manufacturing_pg11(9)mpt3sas_config_get_bios_pg2(9)mpt3sas_config_get_bios_pg3(9)mpt3sas_config_set_bios_pg4(9)mpt3sas_config_get_bios_pg4(9)mpt3sas_config_get_iounit_pg0(9)mpt3sas_config_get_iounit_pg1(9)mpt3sas_config_set_iounit_pg1(9)mpt3sas_config_get_iounit_pg3(9)mpt3sas_config_get_iounit_pg7(9)mpt3sas_config_get_iounit_pg8(9)mpt3sas_config_get_ioc_pg8(9)mpt3sas_config_get_ioc_pg1(9)mpt3sas_config_set_ioc_pg1(9)mpt3sas_config_get_sas_device_pg0(9)mpt3sas_config_get_pcie_device_pg0(9)mpt3sas_config_get_pcie_iounit_pg1(9)mpt3sas_config_get_pcie_device_pg2(9)mpt3sas_config_get_number_hba_phys(9)mpt3sas_config_get_sas_iounit_pg0(9)mpt3sas_config_get_sas_iounit_pg1(9)mpt3sas_config_set_sas_iounit_pg1(9)mpt3sas_config_get_expander_pg0(9)mpt3sas_config_get_expander_pg1(9)mpt3sas_config_get_enclosure_pg0(9)mpt3sas_config_get_phy_pg0(9)mpt3sas_config_get_phy_pg1(9)mpt3sas_config_get_raid_volume_pg1(9)mpt3sas_config_get_number_pds(9)mpt3sas_config_get_raid_volume_pg0(9)mpt3sas_config_get_phys_disk_pg0(9)mpt3sas_config_get_driver_trigger_pg0(9)_config_set_driver_trigger_pg0(9)mpt3sas_config_update_driver_trigger_pg0(9)mpt3sas_config_get_driver_trigger_pg1(9)_config_set_driver_trigger_pg1(9)mpt3sas_config_update_driver_trigger_pg1(9)mpt3sas_config_get_driver_trigger_pg2(9)_config_set_driver_trigger_pg2(9)mpt3sas_config_update_driver_trigger_pg2(9)mpt3sas_config_get_driver_trigger_pg3(9)_config_set_driver_trigger_pg3(9)mpt3sas_config_update_driver_trigger_pg3(9)mpt3sas_config_get_driver_trigger_pg4(9)_config_set_driver_trigger_pg4(9)mpt3sas_config_update_driver_trigger_pg4(9)mpt3sas_config_get_volume_wwid(9)
that's the squad π«Ά and yes i listed every single one, because leaving one out is not the vibe π
heads up bestie: this page lives in ./drivers/scsi/mpt3sas, dated October 2026 β so like, future vibes only πΈ ok bye, go get that volume handle πβ¨π
π¦ 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