libseccomp: filter_db: correctly set next pointer if new syscall is first
libseccomp: filter_db: correctly set next pointer if new syscall is first

If there was a list of syscalls on db->sys_allow/db->sys_deny and we are
adding a new item to the front, the ->next pointer on the new item will
not point to those syscalls already in the list.  So fix ->next.

Signed-off-by: Eric Paris <b0b36e3cd9ea4e5739ff430a3056fabf2fdb0376@redhat.com>
Signed-off-by: Paul Moore <88a1d58bf22a647dce58dd91f9595600dceabba9@redhat.com>

seccomp/libseccomp,seccomp/libseccomp,amluto/libseccomp,amluto/libseccomp,seccomp/libseccomp,amluto/libseccomp