megasas_all...crash_buffer(9)
π megasas_alloc_host_crash_buffer(9) β the crash-dump buffer glow-up
okay so this one lives in the Kernel API Manual bestie, and it's genuinely iconic: it's the function that sets up the host-side buffers so the firmware can dump its crash data. Firmware drama gets collected, no cap. π©·
β¨ NAME β¨
megasas_alloc_host_crash_buffer β Host buffers for Crash dump collection from Firmware
like, literally what it says on the tin: it's the buffer situation for scooping up that crash dump the firmware wants to hand over. π
πΈ SYNOPSIS πΈ
void megasas_alloc_host_crash_buffer (struct megasas_instance *instance
);
yep, one argument, void return, she's lowkey simple and that's the vibe. β¨
π¦ ARGUMENTS π¦
instanceβ Controller's soft instance π«Ά (the per-controller software struct, the main character of this whole file tbh)
β RETURN β
Number of allocated host crash buffers
that's the number you get back β how many host crash buffers ended up allocated. π
heads up though: the synopsis says void while RETURN talks about a count. we're reporting it exactly as written, bestie β not my job to fix their paperwork π
π₯ SEE ALSO π₯
she hangs out in the kernel file here:
./drivers/scsi/megaraid/megaraid_sas_fusion.c
and here's the whole group chat of friends, in order, all of them, every single one π:
megasas_adp_reset_wait_for_ready(9)megasas_check_same_4gb_region(9)megasas_enable_intr_fusion(9)megasas_disable_intr_fusion(9)megasas_get_cmd_fusion(9)megasas_return_cmd_fusion(9)megasas_write_64bit_req_desc(9)megasas_fire_cmd_fusion(9)megasas_fusion_update_can_queue(9)megasas_free_cmds_fusion(9)megasas_create_sg_sense_fusion(9)megasas_alloc_cmds_fusion(9)wait_and_poll(9)megasas_ioc_init_fusion(9)megasas_sync_pd_seq_num(9)megasas_allocate_raid_maps(9)megasas_configure_queue_sizes(9)megasas_free_ioc_init_cmd(9)megasas_init_adapter_fusion(9)megasas_fault_detect_work(9)map_cmd_status(9)megasas_is_prp_possible(9)megasas_make_prp_nvme(9)megasas_make_sgl_fusion(9)megasas_make_sgl(9)megasas_set_pd_lba(9)megasas_stream_detect(9)megasas_set_raidflag_cpu_affinity(9)megasas_build_ldio_fusion(9)megasas_build_ld_nonrw_fusion(9)megasas_build_syspd_fusion(9)megasas_build_io_fusion(9)megasas_build_and_issue_cmd_fusion(9)megasas_complete_r1_command(9)access_irq_context(9)release_irq_context(9)complete_cmd_fusion(9)megasas_enable_irq_poll(9)megasas_sync_irqs(9)megasas_irqpoll(9)megasas_complete_cmd_dpc_fusion(9)megasas_isr_fusion(9)build_mpt_mfi_pass_thru(9)build_mpt_cmd(9)megasas_issue_dcmd_fusion(9)megasas_release_fusion(9)megasas_read_fw_status_reg_fusion(9)megasas_free_host_crash_buffer(9)megasas_adp_reset_fusion(9)megasas_check_reset_fusion(9)megasas_trigger_snap_dump(9)megasas_tm_response_code(9)megasas_issue_tm(9)
mwah π that's the whole page, and here's the cute sign-off: this little number ships out of ./drivers/scsi/megaraid, dated October 2026, and it's filed under the megasas_all...crash_buffer(9) manual slot. slay, go allocate some buffers responsibly π§ββοΈπ
π¦ 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