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
rename(2) makes changes to our data structures without validation that said system call has exited successfully(something we cannot know before we reach syscall exit).
Generally speaking the whole mechanism feels awkward and I'd rather find a better way to do it. Will look into it.
The text was updated successfully, but these errors were encountered:
Well after thinking about it the solution was rather simple:
The only thing that rename_exit cannot access when compared with its rename_entry counterpart is the absolute path of the oldpath. oldpath itself is actually accessible, and the hash is the same as the newpath hash.
rename(2)
makes changes to our data structures without validation that said system call has exited successfully(something we cannot know before we reach syscall exit).Generally speaking the whole mechanism feels awkward and I'd rather find a better way to do it. Will look into it.
The text was updated successfully, but these errors were encountered: