13 Commits (959bd66a1d7796c32fb0d54beb3d71e565a4db2c)

Author	SHA1	Message	Date
Richard Fuchs	ff0cdf8393	MT#55283 store ref to stream object in priv data ... Change-Id: I0c8dcd333770ab3da1fe7fea28deadaca43d4147	4 months ago
Richard Fuchs	11dea691e8	MT#55283 make eof flag atomic ... Change-Id: I0a76772c92bf999d1356dc1b91670ddc7583070a	4 months ago
Andrew Yager	b1aec46de8	MT#55283 kernel-module: detect nft_expr_ops.validate signature via compile test ... 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	4 months ago
Richard Fuchs	14769ec05d	MT#55283 fix refcount release ... Closes #2067 Change-Id: I9fa79d67f158a3b5e00cdc83a12c494a4459f8a9	4 months ago
Richard Fuchs	9a3f33a703	MT#55283 fix stream close race condition ... Using the stream object after dropping the reference is unsafe. Change-Id: I58df474272cc7e168d6d65e5f6ace3a42fe22ef1	5 months ago
Richard Fuchs	454983a3a8	MT#55283 add TOS to kernel player ... Change-Id: I1e13015675b2b539e9c7cde01fba96a912726793	6 months ago
Richard Fuchs	14561524dc	MT#55283 protect against possibly signed int ... and add an additional comment Change-Id: I5cb3f434a21879343568f87425356507c2717d7b	6 months ago
Richard Fuchs	e24245501d	MT#55283 add const qualifiers ... Change-Id: I8351c55fad8d446cd336d645dff8c79410d72967	6 months ago
Richard Fuchs	84ca9e65ba	MT#55283 use kthread_*_stop ... Change-Id: Icf1f8bfbec073fbe7e842cb7671d673bbee5a9dc	6 months ago
Richard Fuchs	900dfd5f86	MT#55283 signed refcount for consistency ... Change-Id: I56008b19b60988127634c70e8703297f6059b93c	7 months ago
Richard Fuchs	4b6b2eb1ab	MT#55283 fix compilation for RHEL ... Closes #2042 Change-Id: I8b0de1bfdfa46370365511809daffd56bfb8a055	7 months ago
root	503c4aaffe	MT#55283 Fix nft_rtpengine compilation on RHEL/AlmaLinux 9.x kernel 5.14 ... Add support for RHEL/AlmaLinux/Rocky Linux 9.x kernels which backport the 'reset' parameter to nft_expr_dump function from kernel 6.2.0. This affects all RHEL 9 family distributions with kernel 5.14. Tested on AlmaLinux 9.7 with kernel 5.14.0-611.11.1.el9_7.x86_64 Closes #2038 Closes #2037 Change-Id: I305be17cdbf7730acbc7d9b978694c7b0eb37b02	8 months ago
Richard Fuchs	b9d1509244	MT#55283 rename module ... Change-Id: I81f5370655af00d3a99593eb17cb1d62d961370c	8 months ago