Open Andreagit97 opened 2 years ago
:partying_face: :balloon:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Probably these suggestions will be part of a final cleanup, when the support to all syscalls will be completed :)
Probably these suggestions will be part of a final cleanup, when the support to all syscalls will be completed :)
What's missing here?
What's missing here?
All points i would say
Now only libpman
cleanup pending?
cc @Andreagit97 ?
nope we miss all the points here
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
@Andreagit97 do you plan to work on this?
(if so please /assign
it to yourself :pray: )
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
@Andreagit97 what's missing here?
all the points in the issue!
all the points in the issue!
got it. Sorry, all those merged icons misled me to think there was some progress.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
/remove-lifecycle stale
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale
.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten
.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close
.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle rotten
/remove-lifecycle rotten
This issue tracks some possible cleanups related to the modern BPF probe
[ ] Some refactoring highlighted by @hbrueckner during reviews (thank you for that) :) These are comments on merged PR that's the reason why it seems that we have already addressed them.
[ ] Remove
libpman
and use directly thescap-modern-bpf-engine
.libpman
was designed before the born of the "new" scap v-table approach. It was a good way to abstract the complexity of the modern probe loading from libscap, and moreover, it helped us in avoiding code duplication in the old modern bpf framework test, but now that we have a dedicated engine for the modern probe and we use directly the engines in the drivers tests, there is probably no more need forlibpman
. Moreover removinglibpman
could help us in improving the logging phase in our libraries :)