Page MenuHomeFreeBSD

bhyve: Move the gdb_active check to gdb_cpu_suspend().
ClosedPublic

Authored by jhb on Apr 1 2021, 4:47 PM.
Tags
None
Referenced Files
F107063126: D29538.id87337.diff
Thu, Jan 9, 12:54 PM
Unknown Object (File)
Mon, Jan 6, 7:04 AM
Unknown Object (File)
Fri, Dec 27, 6:31 AM
Unknown Object (File)
Dec 4 2024, 5:46 AM
Unknown Object (File)
Dec 4 2024, 4:20 AM
Unknown Object (File)
Dec 3 2024, 2:26 AM
Unknown Object (File)
Nov 28 2024, 5:22 PM
Unknown Object (File)
Nov 7 2024, 4:28 AM

Details

Summary

The check needs to be in the public routine (gdb_cpu_suspend()), not
in the internal routine called from various places
(_gdb_cpu_suspend()). All the other callers of _gdb_cpu_suspend()
already check gdb_active, and this breaks the use of snapshots when
the debug server is not enabled since gdb_cpu_suspend() tries to lock
an uninitialized mutex.

Reported by: Darius Mihai, Elena Mihailescu
Fixes: 621b5090487de9fed1b503769702a9a2a27cc7bb

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

jhb requested review of this revision.Apr 1 2021, 4:47 PM

We tested the patch and everything seems OK from our part. The fix works as intended. Thanks!

This revision is now accepted and ready to land.Apr 4 2021, 8:53 AM