aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorMichael Kerrisk (man-pages) <[email protected]>2017-04-27 13:54:11 +0200
committerLinus Torvalds <[email protected]>2017-04-27 10:45:09 -0700
commit59372bbf3abd5b24a7f6f676a3968685c280f955 (patch)
tree1b9fde933d8e9cbd7dec3c39521ca0cb16eed73d /tools/perf/util/scripting-engines/trace-event-python.c
parentf83246089ca09308425175d47f5e71e6da68b2ef (diff)
statx: correct error handling of NULL pathname
The change in commit 1e2f82d1e9d1 ("statx: Kill fd-with-NULL-path support in favour of AT_EMPTY_PATH") to error on a NULL pathname to statx() is inconsistent. It results in the error EINVAL for a NULL pathname. Other system calls with similar APIs (fchownat(), fstatat(), linkat()), return EFAULT. The solution is simply to remove the EINVAL check. As I already pointed out in [1], user_path_at*() and filename_lookup() will handle the NULL pathname as per the other APIs, to correctly produce the error EFAULT. [1] https://lkml.org/lkml/2017/4/26/561 Signed-off-by: Michael Kerrisk <[email protected]> Cc: David Howells <[email protected]> Cc: Al Viro <[email protected]> Cc: Eric Sandeen <[email protected]> Signed-off-by: Linus Torvalds <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions