diff options
| author |   Steve Muckle <smuckle.linux@gmail.com> | 2017-10-12 21:44:57 -0700 |
|---|---|---|
| committer |   Shuah Khan <shuahkh@osg.samsung.com> | 2017-11-15 08:01:42 -0700 |
| commit | 2d80c92d6cae986e8f3f04e64dbea9883680ae1c (patch) | |
| tree | d662412c2bccb69adda61de54848d1ee2305f80f /tools/testing/selftests/memory-hotplug/Makefile | |
| parent | selftests: seccomp: update .gitignore with newly added tests (diff) | |
| download | wireguard-linux-2d80c92d6cae986e8f3f04e64dbea9883680ae1c.tar.xz wireguard-linux-2d80c92d6cae986e8f3f04e64dbea9883680ae1c.zip | |
selftests/exec: include cwd in long path calculation
When creating a pathname close to PATH_MAX to test execveat, factor in
the current working directory path otherwise we end up with an absolute
path that is longer than PATH_MAX. While execveat() may succeed, subsequent
calls to the kernel from the runtime environment which are required to
successfully execute the test binary/script may fail because of this.
To keep the semantics of the test the same, rework the relative pathname
part of the test to be relative to the root directory so it isn't
decreased by the length of the current working directory path.
Signed-off-by: Steve Muckle <smuckle.linux@gmail.com>
Signed-off-by: Shuah Khan <shuahkh@osg.samsung.com>
Diffstat (limited to 'tools/testing/selftests/memory-hotplug/Makefile')
0 files changed, 0 insertions, 0 deletions