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 text was updated successfully, but these errors were encountered:
drossetti
changed the title
concurrent invalidation and tear-down can trigger bogus print
concurrent invalidation and tear-down can trigger use-after-free and possibly kernel memory corruption
Oct 11, 2023
drossetti
changed the title
concurrent invalidation and tear-down can trigger use-after-free and possibly kernel memory corruption
concurrent invalidation and tear-down can trigger a bug
Oct 11, 2023
Updating this issue after a long time.
It turns out that the print is actually a signature of a bug in the way the MR are cleaned up, in specific conditions.
The other relevant diagnostic is the one below:
Both may be related to this issue.
The concerning case is when those checks are not able to mitigate the issue, because of the content of the memory is not zero.
Condition below is benign (see #15 ) so peer_err() below is incorrect and confusing. It should be removed.
The text was updated successfully, but these errors were encountered: