Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

giuseppe
Copy link
Member

@giuseppe giuseppe commented Sep 9, 2019

allow to specify what flags must be passed to seccomp(2) when
installing the filter.

Signed-off-by: Giuseppe Scrivano [email protected]

allow to specify what flags must be passed to seccomp(2) when
installing the filter.

Signed-off-by: Giuseppe Scrivano <[email protected]>
@giuseppe
Copy link
Member Author

giuseppe commented Sep 9, 2019

CC @mrunalp @vbatts

@rhatdan
Copy link
Contributor

rhatdan commented Sep 9, 2019

@caniszczyk @crosbymichael @dqminh @hqhq @mrunalp @philips @tianon @vbatts @vishh PTAL

A couple of reasons for these changes:

We are working on generating seccomp rules per container, and would like to be able to see missing syscalls in the audit.log.

People are not using SECCOMP separation, because it hurts performance by turning on the spectre/meltdown mitigations by default. People who want performance could still use seccomp if we did not turn on the mitigation by default.

@crosbymichael
Copy link
Member

crosbymichael commented Sep 10, 2019

LGTM

Approved with PullApprove

1 similar comment
@hqhq
Copy link
Contributor

hqhq commented Sep 11, 2019

LGTM

Approved with PullApprove

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants