Geyslan Gregório
Geyslan Gregório
Stressed locally two times, one printing to none and the other to a json file. None reproduced the deadlock. The run which generated `351_999_998` events to sink stage: `dist/tracee --metrics...
With all signatures I was able to reproduced it. deadlocks From 270 stack dumps (a dump every 10s): ``` found in 151 dumps: goroutine 4649332 [sync.Mutex.Lock, 2 minutes]: internal/sync.runtime_SemacquireMutex(0xc00078a690?, 0x5?,...
It make sense, but I'm not certain if this is solved.
@ShohamBit you can try changing Vagrantfile to use an image like https://portal.cloud.hashicorp.com/vagrant/discover/perk/ubuntu-20.04-arm64. You need to set it to use qemu as provider instead of vbox.
I totally agree. But before tackling it let's get this one in? https://github.com/aquasecurity/tracee/pull/4279 It has fixes and improvements which need to be followed.
> For those following along, working through this on our fork: [DataDog#7](https://github.com/DataDog/btfhub/issues/7) Nice! @yanivagman FYI about BTF for modules support.
I wasn't able to reproduce this. It was probably solved by https://github.com/aquasecurity/tracee/pull/4003.
> This raises the need to normalize syscall ids at the definition layer. For sure, and as we've discussed priorly, one idea is to use the same ids given to...
Is this still relevant, @yanivagman, since https://github.com/aquasecurity/tracee/pull/4426?
I tested it again since I noticed you removed the recursive loading what made the initial behaviour stands. For each selected event that is a signature, analyze emits an error:...