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
{{ message }}
This repository has been archived by the owner on Feb 26, 2020. It is now read-only.
We should implement a new step that is run after the "zfstest" test suite is run, which would force a kernel crash dump and then run the mdb command ::findleaks against the resultant core dump. This would make it easier to detect kernel memory leaks introduced by new changes in any of the code paths exercised by "zfstest".
If the existing code paths already contain kernel memory leaks, we would have to filter these known leaks, if not fix them prior to adding this automatic detection.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We should implement a new step that is run after the "zfstest" test suite is run, which would force a kernel crash dump and then run the
mdb
command::findleaks
against the resultant core dump. This would make it easier to detect kernel memory leaks introduced by new changes in any of the code paths exercised by "zfstest".If the existing code paths already contain kernel memory leaks, we would have to filter these known leaks, if not fix them prior to adding this automatic detection.
The text was updated successfully, but these errors were encountered: