On Wed, Jun 24, 2026 at 03:08:42PM +0800, Zhang Chen wrote: > Since previous patches introduced explicit monitor tracking and reference > counting via IOThreadHolder during initialization, standard global calls > to iothread_get_aio_context() are no longer appropriate for raw context > fetches. > > Switch the remaining fallback sites in monitor_suspend(), monitor_resume(), > and monitor_init_qmp() to use iothread_unsafe_get_aio_context(). This aligns > with the new safe ref/unref lifecycles introduced for monitor tracking.
Why is the unsafe API used here? monitor_data_init() now takes a reference and gets the AioContext. Can you use that AioContext here instead of fetching it with iothread_unsafe_get_aio_context()?
signature.asc
Description: PGP signature
