This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has posted comments on this change. ( https://gerrit.osmocom.org/c/osmo-gbproxy/+/26319 ) Change subject: gbproxy: Also try to route STATUS messages with truncated PDU in error ...................................................................... Patch Set 2: > Patch Set 2: > Well, we specified doing this from the start. Truncated pdu-in-error can happen if the original pdu was close to the MTU already (e.g. unitdata, RIM messages). Since the BVC is established end-to-end we need to route the STATUS correctly so the offending side can take action and/or report the issue. Ah indeed, STATUS contains the pdu-in-error, then that makes sense. May be worth adding that to the commit message, but it may be obvious to people working on this :) -- To view, visit https://gerrit.osmocom.org/c/osmo-gbproxy/+/26319 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gbproxy Gerrit-Branch: master Gerrit-Change-Id: I173eb8ef6257248e3c893c31486575019a3ef873 Gerrit-Change-Number: 26319 Gerrit-PatchSet: 2 Gerrit-Owner: daniel <dwillmann at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy at sysmocom.de> Gerrit-Reviewer: lynxis lazus <lynxis at fe80.eu> Gerrit-CC: pespin <pespin at sysmocom.de> Gerrit-Comment-Date: Thu, 18 Nov 2021 16:41:35 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20211118/0d86c1ee/attachment.htm>