RTRLIB-Pull-Request Testing

Build: #67 was successful Custom build by Github Hook with revision db2d254d75b835abb169f2f9e4a8cfbe74a3c365

Build result summary

Details

Completed
Duration
8 minutes
Flags
Custom revisionCustom build
Labels
None
Revision
db2d254d75b835abb169f2f9e4a8cfbe74a3c365 db2d254d75b835abb169f2f9e4a8cfbe74a3c365
Successful since
#65 ()

Custom variables

Custom revision
db2d254d75b835abb169f2f9e4a8cfbe74a3c365 db2d254d75b835abb169f2f9e4a8cfbe74a3c365
Name Value
github_base_sha cb3c974523de9c544cffdcf4734cb3dddc5a52ed
github_branch master
github_repo rtrlib/rtrlib

Code commits

Author Commit Message Commit date
Marcel Röthke <marcel.roethke@haw-hamburg.de> Marcel Röthke <marcel.roethke@haw-hamburg.de> db2d254d75b835abb169f2f9e4a8cfbe74a3c365 db2d254d75b835abb169f2f9e4a8cfbe74a3c365 rtrlib/rtr: Ensure shadow tables are only freed when initialized (#204)
From the Bug report:
> If rtr_receive_pdu returns an error code, the execution flow is
> redirected to the cleanup label. If ->is_resetting is now true (e.g.,
> because it was set by a CACHE_RESPONSE PDU processed by
> rtr_handle_cache_response_pdu), pfx_table_free_without_notify and
> spki_table_free_without_notify are executing multiple operations on this
> uninitialized data.

This patch ensures the cleanup code can check whether the shadow tables
have been initialized and only frees them if they are.