-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Bugs in itimer::work()? #1073
Comments
Indeed, I can reproduce the bug with
This ping runs for a random amount of time (different in every run) and then crashes:
relevant part of gdb stack trace is same as you saw:
|
I know where the bug comes from, but still not a good way to fix it. Our The problem is that it appears that ping, and probably other |
I sent a patch titled "alarm(): fix crash when alarm is rearmed from alarm handler" which seems to fix this bug. Please test and review. |
When I test OS'v networking, it is not able to keep sending pings.
It seems that there is a bug in OSv's scheduler (maybe).
Command:
Output:
172.16.0.1: host
172.16.0.2: guest
commit: 4225139
QEMU: QEMU emulator version 2.8.1(Debian 1:2.8+dfsg-6+deb9u8)
OS: Debian 9 with backport kernel
edit 1)
this command also fails...
edit 2)
GDB backtrace. In
wake
, it passes null pointer towake_impl
.The text was updated successfully, but these errors were encountered: