All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shuah Khan <shuahkh@osg.samsung.com>
To: Yannick Brosseau <scientist@fb.com>,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: kernel-team@fb.com
Subject: Re: [PATCH] selftests/exec: Add Makefile to install list since exec test expect it
Date: Tue, 14 Jun 2016 13:22:07 -0600	[thread overview]
Message-ID: <5760595F.4040502@osg.samsung.com> (raw)
In-Reply-To: <ce531f7a-bb10-1be2-e8d4-7a1fdbd7821c@fb.com>

On 06/14/2016 01:15 PM, Yannick Brosseau wrote:
> On 06/14/2016 12:09 PM, Shuah Khan wrote:
>> On 06/14/2016 12:45 PM, Yannick Brosseau wrote:
>>> When running the execveat test once installed, the Makefile it not available and the
>>> test fail. Bundling the Makefile file with the installed files fix that.
>> Install is for installing kselftest binaries and run-time dependencies
>> if any on a target system. It is not for being able to build it on the
>> target. Bundling Makefile doesn't make sense.
> The test tries to exec the Makefile file:
>     fail += check_execveat_fail(dot_dfd, "Makefile", 0, EACCES);
> 
> So it's a runtime dependency at the moment.
> We can either change the test to try to open another file or add the
> Makefile

Ah I see why Makefile is necessary. No point in adding a new file.
Please add a comment in the file to indicate that Makefile is a
run-time dependency. Could you also rephrase the change log to make
it clear that Makefile is run-time dependency.

Thanks for catching it.

-- Shuah

      reply	other threads:[~2016-06-14 19:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 18:45 [PATCH] selftests/exec: Add Makefile to install list since exec test expect it Yannick Brosseau
2016-06-14 19:09 ` Shuah Khan
2016-06-14 19:15   ` Yannick Brosseau
2016-06-14 19:22     ` 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=5760595F.4040502@osg.samsung.com \
    --to=shuahkh@osg.samsung.com \
    --cc=kernel-team@fb.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=scientist@fb.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.