Attention is currently required from: falconia, fixeria.
laforge has posted comments on this change by falconia. (
https://gerrit.osmocom.org/c/libosmo-abis/+/38138?usp=email )
Change subject: trau2rtp FR & EFR: fix uninitialized memory bug
......................................................................
Patch Set 1:
(1 comment)
Patchset:
PS1:
> Alternatively, we may clarify the API docs and
state that it's responsibility of the caller to [ze […]
I agree the current
situation is not good API design - but we have been doing it this way [here] for a long
time. Your patch now means we zero-initialize twice (the implicit memset in talloc_zero
and the explicit one here). Shouldn't hurt performance as the data should be in cache
after the first write, but still it's suboptimal. We also have no way of removing the
memset in the existing code, as we have to keep forward/backward compatibility.
All in all it's dissatisfactory either way. But safety first, so I think we should
merge this.
--
To view, visit
https://gerrit.osmocom.org/c/libosmo-abis/+/38138?usp=email
To unsubscribe, or for help writing mail filters, visit
https://gerrit.osmocom.org/settings?usp=email
Gerrit-MessageType: comment
Gerrit-Project: libosmo-abis
Gerrit-Branch: master
Gerrit-Change-Id: I6e6693e096b920a973c8cc627e94884099d004b5
Gerrit-Change-Number: 38138
Gerrit-PatchSet: 1
Gerrit-Owner: falconia <falcon(a)freecalypso.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Reviewer: laforge <laforge(a)osmocom.org>
Gerrit-Attention: falconia <falcon(a)freecalypso.org>
Gerrit-Attention: fixeria <vyanitskiy(a)sysmocom.de>
Gerrit-Comment-Date: Mon, 16 Sep 2024 07:33:17 +0000
Gerrit-HasComments: Yes
Gerrit-Has-Labels: No
Comment-In-Reply-To: falconia <falcon(a)freecalypso.org>
Comment-In-Reply-To: laforge <laforge(a)osmocom.org>
Comment-In-Reply-To: fixeria <vyanitskiy(a)sysmocom.de>