)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":1000002,"name":"cron2","display_name":"Gert Doering","email":"gert@greenie.muc.de","username":"cron2"},"change_message_id":"94253c21aedf6f121861a2af91d994fe98bbcfdb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1054a1d5_4d35f128","updated":"2024-09-25 15:10:41.000000000","message":"Indeed, this patch makes sense - if it would be NULL, the check is too late, so in this place it does not add anything useful.\n\nAfter staring at the code for quite some time I am reasonably convinced that c2.did_open_tun will only be set if `do_open_tun()` was called, which will either have a previously-set tuntap or will allocate a new one in `do_init_tun()`.\n\n`do_close_tun()` seems to be the only code path that could set `tuntap \u003d NULL` (and it does not clear `did_open_tun`), but it is only called in sequences where it\u0027s either reopened right away, or where the instance ends for good.","commit_id":"ad12105a3318661b293fcb6b5383a95b15ad0806"}]}