[Bug 1932120] Re: callbackRequest potentially accesses uninitialized memory

[Andrew Johnson via Core-talk <core-talk at aps.anl.gov>]

** Changed in: epics-base
    Milestone: None => 7.0.6

** Changed in: epics-base
       Status: New => Fix Committed

-- 
You received this bug notification because you are a member of EPICS
Core Developers, which is subscribed to EPICS Base.
Matching subscriptions: epics-core-list-subscription
https://bugs.launchpad.net/bugs/1932120

Title:
  callbackRequest potentially accesses uninitialized memory

Status in EPICS Base:
  Fix Committed

Bug description:
  If epicsAtomicCmpAndSwapIntT() in callbackInit() fails for some reason
  (e.g. because of bug #1932118), the callback queues never get
  initialized (and callback threads never get started) and the following
  warning is printed during iocInit:

  Warning: callbackInit called again before callbackCleanup

  Nevertheless,  callbackRequest() will use these uninitialized queues
  (and an uninitialized event semaphore) without checking, resulting in
  strange message from a spinLock in the uninitialized queue:

  0x132f380 (timerQueue): epicsSpinLock(0x1fda0b79): Deadlock.
  Recursive lock, missed unlock or block when locked.Thread timerQueue (0x132f380) can't proceed, suspending.

  A patch is attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/epics-base/+bug/1932120/+subscriptions