diff options
author | Eran Ben Elisha <eranbe@mellanox.com> | 2019-01-17 22:59:12 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2019-01-18 23:51:22 +0100 |
commit | c7af343b4e33578b7de91786a3f639c8cfa0d97b (patch) | |
tree | e60cab858369020cc94ce5f569e82d53a62e57f0 /fs/notify/fanotify | |
parent | devlink: Add health reporter create/destroy functionality (diff) | |
download | linux-c7af343b4e33578b7de91786a3f639c8cfa0d97b.tar.xz linux-c7af343b4e33578b7de91786a3f639c8cfa0d97b.zip |
devlink: Add health report functionality
Upon error discover, every driver can report it to the devlink health
mechanism via devlink_health_report function, using the appropriate
reporter registered to it. Driver can pass error specific context which
will be delivered to it as part of the dump / recovery callbacks.
Once an error is reported, devlink health will do the following actions:
* A log is being send to the kernel trace events buffer
* Health status and statistics are being updated for the reporter instance
* Object dump is being taken and stored at the reporter instance (as long
as there is no other dump which is already stored)
* Auto recovery attempt is being done. depends on:
- Auto Recovery configuration
- Grace period vs. time since last recover
Signed-off-by: Eran Ben Elisha <eranbe@mellanox.com>
Reviewed-by: Moshe Shemesh <moshe@mellanox.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'fs/notify/fanotify')
0 files changed, 0 insertions, 0 deletions