-
Notifications
You must be signed in to change notification settings - Fork 386
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Use separate execIDs for clone and subsequent exec events
In ed2dc24 we introduced the clone events and subsequent exec events to have the same execID. An example here is: clone() id=1 exec() id=1 exec() id=1 exit() id=1 This is done in order to have the same execID in exit (and be able to cleanup the process cache in the uswr space). On the other hand, this approach has an issue. Let's assume the following scenario: clone() id=1 kprobe() id=1 exec() id=1 kprobe() id=1 exec() id=1 exit() id=1 If a kprobe event comes OOO we cannot know when this is actually happen (and use the correct process information). In that case if the first kprobe event comes after the first exec we should add this to the eventcache in order to wait for the process info. The previous commit reverts ed2dc24 and this commit enables clone and subsequent exec events to all have a separate (and unique) execID. In order to fix the cleanup issue we send the pid and ktime of the process needed cleanup with the exec event. Using the new approach an example is: clone() id=1 kprobe() id=1 exec() id=2 [will also cleanup id=1] kprobe() id=2 exec() id=3 [will also cleanup id=2] exit() id=3 Signed-off-by: Anastasios Papagiannis <[email protected]>
- Loading branch information
Showing
5 changed files
with
97 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters