Re: [PATCH] selftests/lib: set printf.sh executable

From	Kees Cook <keescook@chromium.org>
Newsgroups	linux.kernel
Subject	Re: [PATCH] selftests/lib: set printf.sh executable
Date	2016-06-18 20:00 +0200
Message-ID	<rLsHf-7cS-1@gated-at.bofh.it> (permalink)
References	<rLkJH-2cZ-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Sat, Jun 18, 2016 at 2:28 AM, SeongJae Park <sj38.park@gmail.com> wrote:
> Test for test_printf module fails always because the test program,
> printf.sh, has no execution permission.  This commit adds execution
> permission to it.
>
> Signed-off-by: SeongJae Park <sj38.park@gmail.com>

Acked-by: Kees Cook <keescook@chromium.org>

(Is this mode change sufficient, or does the selftest infrastructure
need to explicitly set it executable when running?)

-Kees


> ---
>  tools/testing/selftests/lib/printf.sh | 0
>  1 file changed, 0 insertions(+), 0 deletions(-)
>  mode change 100644 => 100755 tools/testing/selftests/lib/printf.sh
>
> diff --git a/tools/testing/selftests/lib/printf.sh b/tools/testing/selftests/lib/printf.sh
> old mode 100644
> new mode 100755
> --
> 1.9.1
>



-- 
Kees Cook
Chrome OS & Brillo Security

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[PATCH] selftests/lib: set printf.sh executable SeongJae Park <sj38.park@gmail.com> - 2016-06-18 11:30 +0200
  Re: [PATCH] selftests/lib: set printf.sh executable Kees Cook <keescook@chromium.org> - 2016-06-18 20:00 +0200

csiph-web