Bug 1896311

+++ This bug was initially created as a clone of Bug #1896309 +++

Description of problem:

spausedd fails with a segmentation fault if the log_perror() function is run. This function's call to log_printf() is missing a format argument. Its format string has three format specifiers but only two arguments in its VA list.

```
static void
log_perror(int priority, const char *s)
{
        int stored_errno;

        stored_errno = errno;

        log_printf(priority, "%s (%u): %s", stored_errno, strerror(stored_errno));
}
```

Running spausedd as a non-root user (thanks honzaf) is an easy way to reproduce the issue, but other error conditions can lead to the same issue in practice. If this happens, spausedd crashes immediately without printing a meaningful error or warning message.

-----

Version-Release number of selected component (if applicable):

spausedd-2.4.5-7.el7

-----

How reproducible:

Always

-----

Steps to Reproduce:

1. Run spausedd as a non-root user.

-----

Actual results:

[testuser@fastvm-rhel-8-0-23 ~]$ spausedd
Nov 10 01:19:49 spausedd: Could not mlockall
Nov 10 01:19:49 spausedd: Segmentation fault (core dumped)

-----

Expected results:

No segmentation fault. Another error message such as "Can't get maximum SCHED_RR priority" or "Can't set SCHED_RR".

--- Additional comment from Reid Wahl on 2020-11-10 09:25:35 UTC ---

Fixed upstream by commit cbb46dcc.