since previous change relating to incomplete metafile's being read while
still being written, there are still circumstances that result in failure
This change tracks last_good_pos after each full section and advances
mf->pos once by parsed buffer prefix so the next read does not skip tail
bytes. The log lines have now been made dbg instead of warnings as they
should be handled correctly on subsequent reads of the file
Closes#2090
Change-Id: I88cf5a5d1702a818301cfc9448bbbc65ee0bf155
Update all linked subscribers, not just the ones involved in the
connect, as they might also need to have their handlers updated.
Change-Id: Ib7a8aa3ca0d0f986bb90a99bf1337b358e96be33
The current LINUX_VERSION_CODE check for the nft_expr_ops.validate
callback signature breaks on distribution kernels that backport the
API change (mainline commit eaf9b2c875ec, merged in 6.12) without
updating LINUX_VERSION_CODE.
For example, Ubuntu 24.04's 6.8.0-103+ kernel (stable patchset
2026-01-27, LP: #2139158) includes this backport, causing DKMS
builds to fail with -Werror=incompatible-pointer-types.
Replace the version-based #if with a compile test in the existing
gen-rtpengine-kmod-flags configure script. The test tries to assign
a 3-param function to .validate -- if it compiles, the old API is
present and NFT_EXPR_OPS_VALIDATE_HAS_DATA is set. If it fails, the
kernel has the new 2-param version.
Also use kbuild's KERNELRELEASE variable (instead of uname -r) to
resolve the kernel build directory, so that compile tests and KSRC
target the correct kernel during cross-version DKMS builds.
Tested against Ubuntu 6.8.0-90 (3-param) and 6.8.0-106 (2-param),
including cross-kernel builds where the running kernel differs from
the DKMS target.
Closes#2085
Change-Id: I4c8e55b94fb98c3fcda9dccb091d0d1c0c67f9aa
Instead of always blindly picking the matching supp codec for the
receiver codec, pick it only if there is no appropriate sink supp codec,
or both are compatible (which implies a payload type mismatch).
Closes#2084
Change-Id: Ie401db500a038f60f3b4286e2067f90674c611df
This can be populated by automated release build tools so that the
version can be known at runtime even in the absence of a git and/or
Debian environment.
Change-Id: If6d55f0ececd9381bf281ea2ead15fccd8da01a3