Harald Welte has submitted this change and it was merged.
Change subject: l1sap: Validate incoming RTP payload, drop bw-efficient AMR
..
l1sap: Validate incoming RTP payload, drop bw-efficient AMR
A recurrent kernel crash in
Patch Set 2: Code-Review+2
--
To view, visit https://gerrit.osmocom.org/6351
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: If0c9233c628c724de4ab74e58e3e2affac79e6d0
Gerrit-PatchSet: 2
Gerrit-Project: osmo-bts
Gerrit-Branch: master
Patch Set 2: Code-Review+1 Verified+1
Tested, works fine.
--
To view, visit https://gerrit.osmocom.org/6351
To unsubscribe, visit https://gerrit.osmocom.org/settings
Gerrit-MessageType: comment
Gerrit-Change-Id: If0c9233c628c724de4ab74e58e3e2affac79e6d0
Gerrit-PatchSet: 2
Gerrit-Project:
Hello Jenkins Builder,
I'd like you to reexamine a change. Please visit
https://gerrit.osmocom.org/6351
to look at the new patch set (#2).
l1sap: Validate incoming RTP payload, drop bw-efficient AMR
A recurrent kernel crash in sysmobts (several kernel versions)
corrupting kernel memory
Patch Set 1: Code-Review-1
-1 As I could test it only with a non-bw-efficient MSC but I'm having problems
right now connecting to the offending MSC sending bw-efficient mode. Once I
test it there (I expect no major problems since I already tested a previous
version of the patch), we can then
Review at https://gerrit.osmocom.org/6351
l1sap: Validate incoming RTP payload, drop bw-efficient AMR
A recurrent kernel crash in sysmobts (several kernel versions)
corrupting kernel memory in random places has been investigated and
reproduced by placing a call against an MSC sending RTP
with
