Page MenuHomeFreeBSD

Fix mpr(4) panics caused by bad drive mapping tables
ClosedPublic

Authored by asomers on Nov 1 2017, 10:00 PM.
Tags
None
Referenced Files
F81584295: D12901.id34643.diff
Thu, Apr 18, 12:23 PM
F81559682: D12901.id34643.diff
Thu, Apr 18, 1:54 AM
F81555876: D12901.id34643.diff
Thu, Apr 18, 12:27 AM
F81555471: D12901.id34647.diff
Thu, Apr 18, 12:16 AM
Unknown Object (File)
Wed, Apr 17, 3:46 PM
Unknown Object (File)
Feb 7 2024, 6:39 AM
Unknown Object (File)
Dec 20 2023, 12:44 AM
Unknown Object (File)
Dec 16 2023, 4:44 PM
Subscribers

Details

Summary

Fix mpr(4) panics caused by bad drive mapping tables

sys/dev/mpr/mpr_mapping.c
If _mapping_process_dpm_pg0 detects inconsistencies in the drive
mapping table (stored in the HBA's NVRAM), abort reading it and
continue to boot as if the mapping table were blank.

Test Plan

Try booting with an mpr card that contains a known-bad mapping table

Diff Detail

Repository
rS FreeBSD src repository - subversion
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

slm requested changes to this revision.Nov 1 2017, 10:26 PM
slm added inline comments.
sys/dev/mpr/mpr_mapping.c
2382 ↗(On Diff #34643)

Doesn't look like you need 'dpm_entry' here.

This revision now requires changes to proceed.Nov 1 2017, 10:26 PM

Fix copypaste error found by slm

This revision is now accepted and ready to land.Nov 2 2017, 2:55 PM
This revision was automatically updated to reflect the committed changes.