From: Alain Spineux <alain@baculasystems.com>
Date: Mon, 19 Oct 2020 16:33:48 +0000 (+0200)
Subject: Fix #6860 DIR crash when VF are started from the scheduler
X-Git-Tag: Release-11.3.2~855
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=555509353b44ffb052610b88059c825ee6273e29;p=thirdparty%2Fbacula.git

Fix #6860 DIR crash when VF are started from the scheduler

- the 2016 feature "to implement MaxVirtualFullInterval" from the
  COMMUNITY add a field to the "class RUN" but forget to initialize it
  to NULL in RUN::clearall() and then got 0x5555555555555555 instead
  this was written in 2016 by Thomas Lohman for the COMMUNITY and
  added in march 2020 for the 12.4.0
- test it with : USE_SCHEDULER=yes REGRESS_DEBUG=1 tests/virtual-backup-test
---

diff --git a/bacula/src/dird/run_conf.c b/bacula/src/dird/run_conf.c
index 4d87ab86e..7ea5f8cad 100644
--- a/bacula/src/dird/run_conf.c
+++ b/bacula/src/dird/run_conf.c
@@ -50,7 +50,7 @@ void RUN::clearall()
    MaxRunSchedTime_set = spool_data =  spool_data_set = accurate = accurate_set = false;
    write_part_after_job = write_part_after_job_set = priority_set = level_set = false;
 
-   pool = next_pool = full_pool = inc_pool = diff_pool = NULL;
+   pool = next_pool = full_pool = inc_pool = diff_pool = vfull_pool = NULL;
    storage  = NULL;
    msgs = NULL;
    since = NULL;