-
Notifications
You must be signed in to change notification settings - Fork 371
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
UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtpengine/12.2.1.5/build/xt_RTPENGINE.c:5156:32 #1814
Labels
Comments
sipwise-jenkins
pushed a commit
that referenced
this issue
Apr 16, 2024
The PT index can be -1 or -2. Ignore RTP stats in this case. fixes #1814 Change-Id: Ifdcdbccad592fd1a27d2b31359861ecb3e725546
sipwise-jenkins
pushed a commit
that referenced
this issue
Apr 16, 2024
The PT index can be -1 or -2. Ignore RTP stats in this case. fixes #1814 Change-Id: Ifdcdbccad592fd1a27d2b31359861ecb3e725546
sipwise-jenkins
pushed a commit
that referenced
this issue
Apr 16, 2024
The PT index can be -1 or -2. Ignore RTP stats in this case. fixes #1814 Change-Id: Ifdcdbccad592fd1a27d2b31359861ecb3e725546
sipwise-jenkins
pushed a commit
that referenced
this issue
Apr 16, 2024
The PT index can be -1 or -2. Ignore RTP stats in this case. fixes #1814 Change-Id: Ifdcdbccad592fd1a27d2b31359861ecb3e725546
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
rtpengine version the issue has been seen with
12.2.1.5-1~bpo12+1
Used distribution and its version
Debian 12
Linux kernel version used
6.8.2-zabbly+
CPU architecture issue was seen on (see
uname -m
)x86_64
Expected behaviour you didn't see
No response
Unexpected behaviour you saw
Every so often I see a UBSAN call trace in my kernel logs related to the rtpengine kernel module. Call trace is attached.
Steps to reproduce the problem
We see it happen occasionally when running production traffic. I have not determined a specific trigger.
Additional program output to the terminal or logs illustrating the issue
Anything else?
Let me know if you need any further details.
The text was updated successfully, but these errors were encountered: