summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2023-05-11NEWS and version updatev3.0-alpha2Maria Matejka
2023-05-11Fix use-after free in thread stopping codeMaria Matejka
2023-05-11BGP: fix listen socket cleanupMaria Matejka
2023-05-11ID Maps are checking whether their pool is lockedMaria Matejka
2023-05-11Properly protecting the route src global index by RCU read lock and atomic ↵Maria Matejka
operations There was a bug occuring when one thread sought for a src by its global id and another one was allocating another src with such an ID that it caused route src global index reallocation. This brief moment of inconsistency led to a rare use-after-free of the old global index block.
2023-05-11Threads take loops fasterMaria Matejka
2023-05-11Channel: configurable feed block sizeMaria Matejka
2023-05-11BGP: proactively rehash prefix hash up to shorten collision listsMaria Matejka
2023-05-09OLocks in BGP must be freed earlyMaria Matejka
2023-05-07IO Loop / Thread Groups Lock moved to level -attrs- to allow for page ↵Maria Matejka
allocation while locked
2023-05-07Fixed loop movement to not collide on LTT_MOVEMaria Matejka
2023-05-07Fix loop dropping routinesMaria Matejka
2023-05-06Fixed a bug in hot page global storageMaria Matejka
The original algorithm was suffering from an ABA race condition: A: fp = page_stack B: completely allocates the same page and writes into it some data A: unsuspecting, loads (invalid) next = fp->next B: finishes working with the page and returns it back to page_stack A: compare-exchange page_stack: fp => next succeeds and writes garbage to page_stack Fixed this by using an implicit spinlock in hot page allocator.
2023-05-06Debug: keep a circular log of memory page operationsMaria Matejka
2023-05-06Fixed cold page cache leakMaria Matejka
The empty_pages pointer wasn't being propagated into the ->next pointer when more empty_pages were to be stored
2023-05-06Hostentry: fix pool lockingMaria Matejka
2023-05-06Linpool state save and restore refactoringMaria Matejka
2023-05-06Debug: Explicit mprotect() on freed pages to better locate use-after-free bugsMaria Matejka
2023-05-06Page allocator: indentation of messy ifdef blocksMaria Matejka
2023-05-06First try of loop balancingMaria Matejka
If a thread encounters timeout == 0 for poll, it considers itself "busy" and with some hysteresis it tries to drop loops for others to pick and thus better distribute work between threads.
2023-05-03Allocation from linpools and slabs requires the appropriate lock to be takenMaria Matejka
2023-05-03Linpool flushes unused pages even on lp_restore()Maria Matejka
2023-05-03Fixed race condition in hostentry allocationMaria Matejka
2023-05-03Show threads: Fixed problems with CLI buffer reallocationMaria Matejka
... by allocating all the output locally and then sending it out at once.
2023-05-03Explicitly counting loops and threadsMaria Matejka
2023-05-03Loop spent time refactored to separate structures and functionsMaria Matejka
2023-04-26Loops track also locking timeMaria Matejka
2023-04-26IO loops now actually measuring their time (show threads all works)Maria Matejka
2023-04-25Refactoring of domains connected to poolsMaria Matejka
2023-04-24Fix of failing show threads commandMaria Matejka
2023-04-24Merge commit 'd61505b039bf0aa6697e28b2a4e07907c89ba1fb' into thread-nextMaria Matejka
2023-04-24Merge branch 'mq-resource-locking' into thread-nextMaria Matejka
2023-04-24Removed duplicate version 3.0-alpha0 newsMaria Matejka
2023-04-24Resource pools are now bound with domains.Maria Matejka
Memory allocation is a fragile part of BIRD and we need checking that everybody is using the resource pools in an appropriate way. To assure this, all the resource pools are associated with locking domains and every resource manipulation is thoroughly checked whether the appropriate locking domain is locked. With transitive resource manipulation like resource dumping or mass free operations, domains are locked and unlocked on the go, thus we require pool domains to have higher order than their parent to allow for this transitive operations. Adding pool locking revealed some cases of insecure memory manipulation and this commit fixes that as well.
2023-04-22Protocols and tables now use the birdloop pools as primaryMaria Matejka
2023-04-22Resource pool closing has its dedicated functionMaria Matejka
2023-04-22Socket closing has its dedicated functionMaria Matejka
2023-04-22Global protocol list is typed to avoid typecast confusionMaria Matejka
2023-04-22Typed lists: added add_after() and unit testsMaria Matejka
2023-04-21Alpha0 news addedv3.0-alpha1Ondrej Filip
2023-04-21BSD: IPv4 over IPv6 nexthop support on FreeBSDLuiz Amaral
The support for IPv4 routes with IPv6 nexthops was implemented in FreeBSD 13.1, this patch allows to import and export such routes from/to kernel. Minor change from committer.
2023-04-20Linpool: Fix lp_restore()Maria Matejka
When lp_save() is called on an empty linpool, then some allocation is done, then lp_restore() is called, the linpool is restored but the used chunks are inaccessible. Fix it.
2023-04-19Typed lists keep an explicit pointer to the list head.Maria Matejka
This change adds one pointer worth of memory to every list node. Keeping this information helps auditing the lists, checking that the node indeed is outside of list or inside the right one. The typed lists shouldn't be used anywhere with memory pressure anyway, thus the one added pointer isn't significant.
2023-04-18Updated the version number to not include dash (breaks RPM)Maria Matejka
2023-04-18NEWS and version updateMaria Matejka
2023-04-18Merge tag '3.0-alpha0' into HEADMaria Matejka
3.0-alpha0
2023-04-17IO: added a specific loop pickup group for BFD; to be done better in futureMaria Matejka
2023-04-14Merge commit '9e44ace3' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit 'f881b98d' into thread-next-ifaceMaria Matejka
2023-04-14Merge commit '231c6385' into thread-next-ifaceMaria Matejka
generated by cgit v1.2.3 (git 2.39.1) at 2024-11-30 11:08:52 +0000