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.

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

ebpf: fall back to proc parsing when we detect a late event #2334

Closed
iaguis opened this issue Mar 14, 2017 · 0 comments
Closed

ebpf: fall back to proc parsing when we detect a late event #2334

iaguis opened this issue Mar 14, 2017 · 0 comments
Assignees
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@iaguis
Copy link
Contributor

iaguis commented Mar 14, 2017

There is a kernel bug introduced by torvalds/linux@27727df (see bcc's report) that makes timestamps be wrong and results in messages like this in scope's logs:

<probe> ERRO: 2017/03/13 12:33:19.623907 ERROR: late event!

Moreover, this can result in connectevents closely followed by close events to be in reverse order, causing the connection to never disappear from scope.

This bug was introduced in 4.8 but was backported to older kernels by distros. The fix was included in 4.9 and also backported. For example, in Ubuntu, the bug was introduced in kernel 4.4.0-42 and it's not fixed until kernel 4.4.0-51.

We should fall back to proc parsing when we detect a late event.

cc @alban @schu

@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label Mar 14, 2017
@2opremio 2opremio added this to the 1.3 milestone Mar 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

3 participants