This is a collection of changes over the holidays at the end of 2023 / start of 2024. It's mostly cleanup, but needed as I work towards fixing the page allocation.
Of these changes, commit 456d3bc04c68e8cb5428532ff6d0dbe4ced50f8f is the most likely to break stuff, because it's not clear how to trigger the error that it's meant to work around. If it does regress, I expect it would have minor impact - broken packet error counts and some packet drops.
Commit 6142a68df5876a1ac97aa446e064fe4d0679ded9 will cause a warning to be logged for a problem that's existed for a long time. The fix isn't obvious or ready yet, but the warning doesn't make anything worse. It's just motivation/awareness to get to it.
Commit b3da1b213168e9656da6a05244bd906589c879be covers another real bug that could cause memory corruption. A proper fix will come later when the page allocation/reuse code gets reworked.
This is a collection of changes over the holidays at the end of 2023 / start of 2024. It's mostly cleanup, but needed as I work towards fixing the page allocation.
Of these changes, commit 456d3bc04c68e8cb5428532ff6d0dbe4ced50f8f is the most likely to break stuff, because it's not clear how to trigger the error that it's meant to work around. If it does regress, I expect it would have minor impact - broken packet error counts and some packet drops.
Commit 6142a68df5876a1ac97aa446e064fe4d0679ded9 will cause a warning to be logged for a problem that's existed for a long time. The fix isn't obvious or ready yet, but the warning doesn't make anything worse. It's just motivation/awareness to get to it.
Commit b3da1b213168e9656da6a05244bd906589c879be covers another real bug that could cause memory corruption. A proper fix will come later when the page allocation/reuse code gets reworked.