Re: [PATCH v2] selftests/exec: include cwd in long path calculation

2017-10-17 Thread Shuah Khan
On 10/12/2017 10:44 PM, Steve Muckle wrote: > 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

Re: [PATCH v2] selftests/exec: include cwd in long path calculation

2017-10-17 Thread Shuah Khan
On 10/12/2017 10:44 PM, Steve Muckle wrote: > 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

[PATCH v2] selftests/exec: include cwd in long path calculation

2017-10-12 Thread Steve Muckle
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

[PATCH v2] selftests/exec: include cwd in long path calculation

2017-10-12 Thread Steve Muckle
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