adcsensor: Check if the object is still valid in the async callback functions

Sometimes adcsesnor will crash during stress test.
The root cause is that the object is destroyed already
when the async callback functions are executed.
The timer cancel() cannot cancel the expired callback
handlers. When the callback handler is executed,
the object is deleted already.
The buffer used by async_read_util must guarantee
that they remain valid until the handler is called.

Using the weak_ptr to check if the object is still valid
before using these member variables/functions.

Tested:
No adcsensor crash with stress test,
Change the threshold of ADC sensor 0x51 P3VBAT:
while [ true ]; do; \
ipmitool raw 4 0x26 0x51 0x1b 0x20 0x1b 0 0x2a 0x2a 0;\
 ipmitool raw 4 0x26 0x51 0x1b 0x20 0x1b 0 0x2a 0x2b 0;\
 sleep 1; done

Signed-off-by: Yong Li <yong.b.li@linux.intel.com>
Change-Id: I2ddb934199e2d0f52a1a6df25c46eadfe06cfda3
3 files changed
tree: f6a378c0f087111813900c4435f00a489c492a9f
  1. cmake/
  2. include/
  3. service_files/
  4. src/
  5. tests/
  6. .clang-format
  7. .clang-ignore
  8. .gitignore
  9. cmake-format.json
  10. CMakeLists.txt
  11. Jenkinsfile
  12. LICENSE
  13. MAINTAINERS
  14. README.md
README.md

dbus-sensors

dbus-sensors is a collection of sensor applications that provide the xyz.openbmc_project.Sensor collection of interfaces. They read sensor values from hwmon, d-bus, or direct driver access to provide readings. Some advance non-sensor features such as fan presence, pwm control, and automatic cpu detection (x86) are also supported.

key features

  • runtime re-configurable from d-bus (entity-manager or the like)

  • isolated: each sensor type is isolated into its own daemon, so a bug in one sensor is unlikely to affect another, and single sensor modifications are possible

  • async single-threaded: uses sdbusplus/asio bindings

  • multiple data inputs: hwmon, d-bus, direct driver access