Page MenuHomeFreeBSD

Use MTX_SYSINIT for the VESA lock.
ClosedPublic

Authored by jhb on Jul 22 2016, 9:31 PM.
Tags
None
Referenced Files
F166883933: D7290.id18690.diff
Mon, Aug 17, 12:34 PM
F166848187: D7290.id18699.diff
Mon, Aug 17, 2:07 AM
F166848162: D7290.id18699.diff
Mon, Aug 17, 2:06 AM
F166847677: D7290.id18689.diff
Mon, Aug 17, 1:57 AM
F166847676: D7290.id18690.diff
Mon, Aug 17, 1:57 AM
F166847035: D7290.diff
Mon, Aug 17, 1:45 AM
F166846933: D7290.id18699.diff
Mon, Aug 17, 1:44 AM
F166833872: D7290.id18690.diff
Sun, Aug 16, 9:55 PM
Subscribers

Details

Summary

Use MTX_SYSINIT for the VESA lock.

vesa_init_done isn't a reliable guard for the mutex init. If
vesa_configure() doesn't find valid VESA info it will not set
vesa_init_done, but the lock will remain initialized. Revert r303076
and use MTX_SYSINIT to deterministically init the lock.

Diff Detail

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

Event Timeline

jhb retitled this revision from to Use MTX_SYSINIT for the VESA lock..
jhb updated this object.
jhb edited the test plan for this revision. (Show Details)
jhb added reviewers: royger, dumbbell.
  • Don't explicitly destroy the lock.
royger edited edge metadata.

I cannot test this ATM (I might be able to do it tomorrow), but it looks fine, and AFAICT it should also solve the issue I was seeing. Thanks for taking care of this (and sorry for messing it up)!

This revision is now accepted and ready to land.Jul 23 2016, 9:43 AM

Oh, forgot to ask, but since I'm not going to MFC r303076 could you please MFC this to stable/11?

Thanks.

This revision was automatically updated to reflect the committed changes.