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
F172991536: D29538.id.diff
Tue, Sep 22, 5:01 PM
F172959200: D29538.id87337.diff
Tue, Sep 22, 10:20 AM
Unknown Object (File)
Thu, Sep 17, 11:58 PM
Unknown Object (File)
Tue, Sep 15, 10:11 PM
Unknown Object (File)
Fri, Sep 11, 7:16 AM
Unknown Object (File)
Fri, Sep 4, 6:26 AM
Unknown Object (File)
Tue, Sep 1, 5:35 PM
Unknown Object (File)
Aug 23 2026, 4:40 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