From: Shuah Khan <shuah@kernel.org>
To: Steve Muckle <smuckle.linux@gmail.com>
Cc: David Drysdale <drysdale@google.com>,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Shuah Khan <shuah@kernel.org>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [PATCH v2] selftests/exec: include cwd in long path calculation
Date: Tue, 17 Oct 2017 08:15:55 -0600 [thread overview]
Message-ID: <d0da8cd0-e534-5914-ecc5-9483c1bd2407@kernel.org> (raw)
In-Reply-To: <20171013044457.15921-1-smuckle.linux@gmail.com>
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 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>
Thanks for the patch. I plan to get this into 4.15-rc1
-- Shuah
prev parent reply other threads:[~2017-10-17 14:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-13 4:44 [PATCH v2] selftests/exec: include cwd in long path calculation Steve Muckle
2017-10-17 14:15 ` Shuah Khan [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d0da8cd0-e534-5914-ecc5-9483c1bd2407@kernel.org \
--to=shuah@kernel.org \
--cc=drysdale@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=shuahkh@osg.samsung.com \
--cc=smuckle.linux@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox