You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The sd_bus_add_match() method may return a lot of possible errors - ENOBUFS, ECHILD, EINVAL, etc. In sdbusplus/bus/match.hpp, in match() call the return code of sd_bus_add_match() is not checked, due to which the targeted watchers/listeners may silently fail without reporting anything to the end user.
For instance, some machine having a lot of sensors may have a lot of watchers for them.
However, after exceeding watcher/matchers limit it will not set up any new matches at all.
Another example: if there some typo in 'path', it will be silently eaten by sdbusplus interface.
The text was updated successfully, but these errors were encountered:
The sd_bus_add_match() method may return a lot of possible errors - ENOBUFS, ECHILD, EINVAL, etc. In sdbusplus/bus/match.hpp, in match() call the return code of sd_bus_add_match() is not checked, due to which the targeted watchers/listeners may silently fail without reporting anything to the end user.
For instance, some machine having a lot of sensors may have a lot of watchers for them.
However, after exceeding watcher/matchers limit it will not set up any new matches at all.
Another example: if there some typo in 'path', it will be silently eaten by sdbusplus interface.
The text was updated successfully, but these errors were encountered: