seccomp: avoid shadowing of 'action' variable
This is confusing as one 'action' variable is used for storing a SCMP_ enum value, while the other 'action' variable is used for storing a SECCOMP_ enum value. Signed-off-by: Daniel P. Berrangé <berrange@redhat.com> Message-ID: <20230922160644.438631-3-berrange@redhat.com> Reviewed-by: Markus Armbruster <armbru@redhat.com> Signed-off-by: Markus Armbruster <armbru@redhat.com>
This commit is contained in:
parent
3cc9fe177f
commit
0d57919acf
@ -283,9 +283,9 @@ static uint32_t qemu_seccomp_update_action(uint32_t action)
|
||||
if (action == SCMP_ACT_TRAP) {
|
||||
static int kill_process = -1;
|
||||
if (kill_process == -1) {
|
||||
uint32_t action = SECCOMP_RET_KILL_PROCESS;
|
||||
uint32_t testaction = SECCOMP_RET_KILL_PROCESS;
|
||||
|
||||
if (qemu_seccomp(SECCOMP_GET_ACTION_AVAIL, 0, &action) == 0) {
|
||||
if (qemu_seccomp(SECCOMP_GET_ACTION_AVAIL, 0, &testaction) == 0) {
|
||||
kill_process = 1;
|
||||
} else {
|
||||
kill_process = 0;
|
||||
|
Loading…
x
Reference in New Issue
Block a user