Turns out this never worked, ever.  What used to happen is if the protocol_version that was
read in didn't match the rpc_version given to unpack things was just 0.  What this does
now is set the rpc_version to what was stored making it all good.

Bug 3431

burst_buffer/cray - Fix race condition that could cause multiple batch job
    launch requests resulting in downed nodes.
bug 3366

This reverts commit b9bff82f.

slurmctld/agent race condition fix: Prevent job launch while PrologSlurmctld
    daemon is running or node boot in progress.
bug 3366

If a lower version client would try to communicate with a higher version
controller the dbd would return the controller's version and the client
would use that version to talk to the controller. When the controller
would respond, the client wouldn't know how to unpack the higher version
msg.

Bug 3398

bug 3099

This reverts commit e92b49d3.

instead of also in the backfill scheduler.

Bug 3405.

acct_policy_job_runnable_pre_select() calls assoc_mgr_set_qos_tres_cnt()
without tres READ_LOCK.

Note that existing code does not modify the tres structures, so this
cannot currently lead to a race condition.

Bug 3406.

job_submit/cnode was previously removed by commit 63bc71ed.

Bug 3403.

burst_buffer/cray - Avoid "pre_run" operation if not using buffer (i.e.
    just creating or deleting a persistent burst buffer).
bug 3391

Previous job state information was "PENDING" rather than "REQUEUED"
  for each job requeued due to a burst buffer error.
bug 3388

scheduling a Datawarp job.

The assoc_mgr lock needs to happen before the bb_state.bb_mutex.  One place
this could cause deadlock is from src/slurmctld/controller.c
_accounting_cluster_ready() which calls clusteracct_storage_g_cluster_tres
which inturn calls bb_g_job_set_tres_cnt which calls bb_p_job_set_tres_cnt
which will lock the bb_muxtex after the assoc_mgr is already locked.

Bug 3389

Cache results of bit_set_count() calls.

Bug 3393.

backfill scheduler: Stop trying to determine expected start time for a job
    after 2 seconds of wall time. This can happen if there are many running jobs
    and a pending job can not be started soon.
byg 3373

Bug 3364.

Bug 3376.

Fix security issue caused by insecure file path handling triggered by
the failure of a Prolog script. To exploit this a user needs to
anticipate or cause the Prolog to fail for their job.

(This commit is slightly different from the fix to the 15.08 branch.)

CVE-2016-10030.

Fix security issue caused by insecure file path handling triggered by
the failure of a Prolog script. To exploit this a user needs to
anticipate or cause the Prolog to fail for their job.

CVE-2016-10030.

Prevent "stray" jobs from using resources when the srun/salloc
will never launch the actual compute tasks.

Bug 3344.

PluginDir is allowed to be a PATH-style list of directories; remove
incorrect test of the variable as if it were a single directory and
comment that the check for that is elsewhere.

Bug 3361.

Null terminate before strchr().

This is a new message when "PrologFlags=contain" or
  "PrologFlags=alloc" is configured.
bug 3351

Cancel interactive job if Prolog failure with "PrologFlags=contain"
    configured.
bug 3351

Do not allocate specialized cores to jobs using the --exclusive option.
bug 3349

Fix memory and file descriptor leaks in slurmd daemon's sbcast logic.

The part_ptr is sent into the function, there is no reason to look it up
again.  Coverity reported this.

version is lower than the min version, set it to the min.

Bug 3050

sched/backfill - Fix logic to reserve resources for jobs that require a
    node reboot (i.e. to change KNL mode) in order to start.
bug 3346

go into JobAdminHeld.

Bug 3201