Re: [pve-devel] [PATCH frr] frr: fix bit flag collision in patch

2025-03-14 Thread Gabriel Goller
On 14.03.2025 10:33, Thomas Lamprecht wrote: On 13/03/2025 16:49, Gabriel Goller wrote: On 13.03.2025 16:16, Thomas Lamprecht wrote: w.r.t. versioning I'd have bumped the pve1 part to pve2. So '10.2.1-1+pve2'? Exactly. + * fix fabricd dummy_as_loopback flag collision collision with wha

[pve-devel] [PATCH v2 1/2] isisd: fix bit flag collision in options field

2025-03-14 Thread Gabriel Goller
Resolve conflict between F_ISIS_UNIT_TEST and ISIS_OPT_DUMMY_AS_LOOPBACK which were both using the same bit value (0x01). This collision caused unit test mode to be unintentionally enabled when DUMMY_AS_LOOPBACK was set. Link: https://github.com/FRRouting/frr/pull/18377 Fixes: ecf591e ("frr: add t

[pve-devel] [PATCH v2 2/2] bump version to 10.2.1-1+pve2

2025-03-14 Thread Gabriel Goller
This fixes the fabricd dummy_as_loopback flag introduced in an earlier patch. Signed-off-by: Gabriel Goller --- debian/changelog | 8 1 file changed, 8 insertions(+) diff --git a/debian/changelog b/debian/changelog index 6e68311132b1..ff8c9109b486 100644 --- a/debian/changelog +++ b/de

Re: [pve-devel] [PATCH frr] frr: fix bit flag collision in patch

2025-03-14 Thread Thomas Lamprecht
On 13/03/2025 16:49, Gabriel Goller wrote: > On 13.03.2025 16:16, Thomas Lamprecht wrote: >> w.r.t. versioning I'd have bumped the pve1 part to pve2. > > So '10.2.1-1+pve2'? Exactly. >>> + * fix fabricd dummy_as_loopback flag collision >> >> collision with what? these entries should be telling

[pve-devel] [PATCH pve-common] common: procfs: use MemAvailable from kernel to compute memused

2025-03-14 Thread Dietmar Maurer
The current code does not consider "SReclaimable" as cached memory, which can lead to totally wrong values for memfree/memused. This fix uses MemAvailable to compute memused, and returns MemFree without adding buffers and caches. This corrensponds to the values displayed by the "free" command line