- 07 Feb, 2024 40 commits
-
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
we only jump to the again label if we did not get a reference.
-
Nils Goroll authored
Motivated by #40
-
Nils Goroll authored
CID#469253
-
Nils Goroll authored
CID#469261
-
Nils Goroll authored
Coverity CID#469242
-
Nils Goroll authored
Coverity CID#469229
-
Nils Goroll authored
To address some Coverity pedentry with minor impact (at most) CID#469230
-
Nils Goroll authored
Coverity CID#469233
-
Nils Goroll authored
Spotted by Coverity CID#469228, but it is irrelevant because only in test code
-
Nils Goroll authored
Good catch by Coverity CID#469254
-
Nils Goroll authored
Coverity CID#469252
-
Nils Goroll authored
Ref Coverity CID#469262
-
Nils Goroll authored
The optimized case for multiple segments from the same fco did not work as expected, continue did not continue the inner loop. Spotted by Coverity, CID#469236
-
Nils Goroll authored
Coverity CID#469225
-
Nils Goroll authored
Ref CID#469268
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
Motivated by #41
-
Nils Goroll authored
-
Nils Goroll authored
the disk object is always a multiple of 4K, and for higher values (like 12K), rounding up to the next power of two does not make sense. So, just use two allocations for FCO and FDO always.
-
Nils Goroll authored
-
Nils Goroll authored
For now, this uses a local installation of coverity's tools in the slink subfolder.
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
-
Nils Goroll authored
As the fdr argument is from fbo->region, we should DTRT for this situation and not bloat the code with a loop and stuff... Motivated by #39
-
Nils Goroll authored
The code accepted the right pointer, the right offset _OR_ the right size. Which lead to the wrong (usually the last) segment being freed. Fixes #39
-
Nils Goroll authored
... in fellow_busy_obj_trimstore(): The code did not work correctly when the region was to be removed (because it was reduced to size zero) _and_ it was not the last of the regions. Part of the fix for #39
-
Nils Goroll authored
-
Nils Goroll authored
assert that the FCS_BUSY segment to be trimmed is in fact contained in the current body region.
-
Nils Goroll authored
-
Nils Goroll authored
The previous code - if (fdsl->nsegs == fcsl->lsegs || - fcsl->segs[fdsl->nsegs].state == FCS_INIT) { was confusing, it relied on the fact that, when an fcsl has more segments than an fdsl, the first "surplus" segment has state FCS_INIT, when it makes much more sense to just check fdsl->nsegs against fdsl->lsegs.
-
Nils Goroll authored
-