Skip to contentSkip to conversation

Problem with exit status auditing of execve syscall

DISCUSSION Heiko Carstens 1 participant 1 message May 29, 2009 1 message not in the archive s390

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 6 lines · Tony Jones

Anyone have any idea on what is causing the following:

# auditctl -e 1
# auditctl -a entry,always -S execve
# /bin/true
Quoted 8 lines

Causes the following to be logged in /var/log/audit/audit.log

type=SYSCALL msg=audit(1243557456.840:32): arch=80000016 syscall=11 per=400000 success=yes exit=11 ...

Specific to S390 and the execve syscall. I looked through the arch code but I'm not seeing why on the exec case the exit code contains the syscall#.

Above reproduced on 2.6.30-rc7-git2.

The return value of execve on success is not defined.

If it succeeds s390 does not return the return value of the system call. Instead it returns whatever is contained in the current pt_regs structure on the kernel stack that belongs to user space.
The pt_regs structure was changed by the load_binary handler that belongs to the exec format of the executed file. If the ABI of an exec format would require a special return value in r2 it wouldn't be good if we would overwrite it with 0 on success of execve.

In any case, this isn't bug.