Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add check for "is an open for reading/writing". #610

Merged
merged 1 commit into from
Jun 28, 2016
Merged

Add check for "is an open for reading/writing". #610

merged 1 commit into from
Jun 28, 2016

Commits on Jun 27, 2016

  1. Add check for "is an open for reading/writing". 

    While working on measuring performance for falco, I found that one of
the rule bottlenecks was checking for an open for reading/open for
writing. With the current libsinsp, you have to do a string comparison
on the flags argument, which can be slow, especially if you have to
check for multiple flags.

Fix this by adding a check evt.is_open_{read,write} that returns a
boolean based on the value of the flags argument to the corresponding
open/openat. This is similar to the current evt.is_io_{read,write}, but
is argument-specific and limited to open/openat calls.
    @mstemm
    mstemm committed Jun 27, 2016
    Configuration menu
    Copy the full SHA
    8c7f3fb View commit details
    Browse the repository at this point in the history