https://bugs.kde.org/show_bug.cgi?id=506813
Bug ID: 506813
Summary: execveat wrapper need to do more checking
Classification: Developer tools
Product: valgrind
Version First unspecified
Reported In:
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: ---
The LTP execveat02 testcase fails:
execveat_errno.c:17: TFAIL: execveat() passes unexpectedly
execveat02.c:59: TFAIL: execveat() fails unexpectedly, expected: ELOOP: ENOENT
(2)
Which the test case describes as:
2) execveat() fails and returns EINVAL if flag specified is invalid.
3) execveat() fails and returns ELOOP if the file identified by dirfd and
pathname is a symbolic link and flag includes AT_SYMLINK_NOFOLLOW.
The PRE(sys_execveat) in coregrind/m_syswrap/syswrap-linux.c dies various
checks and as if it is the execveat syscall and then tries to uses
handle_pre_sys_execve to execve (resolving the path first if necessary).
The wrapper seems to not follow the execveat checking accurately. Specifically,
it only seems to do various checks when the path is relative, but not when it
is an absolute path.
--
You are receiving this mail because:
You are watching all bug changes.
