From: Linus Torvalds <torvalds@linux-foundation.org>
To: kernel test robot <rong.a.chen@intel.com>
Cc: Uladzislau Rezki <urezki@gmail.com>,
Shuah Khan <shuah@kernel.org>, Kees Cook <keescook@chromium.org>,
Matthew Wilcox <willy@infradead.org>,
Michal Hocko <mhocko@suse.com>,
Oleksiy Avramchenko <oleksiy.avramchenko@sonymobile.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
lkp@01.org
Subject: Re: [LKP] [selftests/vm] a05ef00c97: kernel_selftests.vm.vmalloc_stability_smoke_test.fail
Date: Mon, 11 Mar 2019 10:20:06 -0700 [thread overview]
Message-ID: <CAHk-=wj2TzOJqCr0-J5H6w=d5DgAtVQBQNrYHzaTMkEwkZrwnA@mail.gmail.com> (raw)
In-Reply-To: <20190311074315.GD10839@shao2-debian>
On Mon, Mar 11, 2019 at 12:43 AM kernel test robot
<rong.a.chen@intel.com> wrote:
>
> ./run_vmtests: line 217: ./test_vmalloc.sh: Permission denied
I marked that script executable:
6bc3fe8e7e17 ("tools: mark 'test_vmalloc.sh' executable")
although perhaps the better fix would have been to explicitly use the
shell to start it in the 'run_vmtests' script instead?
We have a lot of files that aren't marked executable, probably because
they came in as (or were generated as) non-git patches. Often through
Andrew's workflow.
But most of them don't seem to matter, because they get run using
explicit script engines. So I only fixed up this one case.
Linus
next parent reply other threads:[~2019-03-11 17:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190311074315.GD10839@shao2-debian>
2019-03-11 17:20 ` Linus Torvalds [this message]
2019-03-11 21:56 ` [LKP] [selftests/vm] a05ef00c97: kernel_selftests.vm.vmalloc_stability_smoke_test.fail Andrew Morton
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='CAHk-=wj2TzOJqCr0-J5H6w=d5DgAtVQBQNrYHzaTMkEwkZrwnA@mail.gmail.com' \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mhocko@suse.com \
--cc=oleksiy.avramchenko@sonymobile.com \
--cc=rong.a.chen@intel.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=urezki@gmail.com \
--cc=willy@infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).