From: Sumit Semwal <sumit.semwal@linaro.org>
To: Kees Cook <keescook@chromium.org>, luto@amacapital.net
Cc: Brian Norris <computersforpeace@gmail.com>,
mcgrof@kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org, linux-kselftest@vger.kernel.org,
Shuah Khan <shuah@kernel.org>
Subject: seccomp ptrace selftest failures with 4.4-stable [Was: Re: LTS testing with latest kselftests - some failures]
Date: Thu, 22 Jun 2017 21:48:19 +0530 [thread overview]
Message-ID: <CAO_48GFi4TRGDtqo8aPPerpQG5ei+dszrGq_0_t_8A2G-03rvQ@mail.gmail.com> (raw)
Hi Kees, Andy,
On 15 June 2017 at 23:26, Sumit Semwal <sumit.semwal@linaro.org> wrote:
> 3. 'seccomp ptrace hole closure' patches got added in 4.7 [3] -
> feature and test together.
> - This one also seems like a security hole being closed, and the
> 'feature' could be a candidate for stable backports, but Arnd tried
> that, and it was quite non-trivial. So perhaps we'll need some help
> from the subsystem developers here.
Could you please help us sort this out? Our goal is to help Greg with
testing stable kernels, and currently the seccomp tests fail due to
missing feature (seccomp ptrace hole closure) getting tested via
latest kselftest.
If you feel the feature isn't a stable candidate, then could you
please help make the test degrade gracefully in its absence?
Greatly appreciated!
Thanks and best regards,
Sumit
next reply other threads:[~2017-06-22 16:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-22 16:18 Sumit Semwal [this message]
2017-06-22 16:53 ` seccomp ptrace selftest failures with 4.4-stable [Was: Re: LTS testing with latest kselftests - some failures] Kees Cook
2017-06-22 17:09 ` Shuah Khan
2017-06-22 17:49 ` Andy Lutomirski
2017-06-22 17:50 ` Kees Cook
2017-06-22 19:06 ` Shuah Khan
2017-06-22 19:48 ` Tom Gall
2017-06-22 20:23 ` Shuah Khan
2017-06-23 4:02 ` Sumit Semwal
2017-06-23 15:36 ` Shuah Khan
2017-06-23 19:03 ` Shuah Khan
2017-06-23 19:44 ` Tom Gall
2017-06-23 1:52 ` Greg Kroah-Hartman
2017-06-23 2:40 ` Andy Lutomirski
2017-06-23 4:05 ` Kees Cook
2017-06-24 0:34 ` Luis R. Rodriguez
2017-06-24 4:45 ` Greg Kroah-Hartman
2017-06-26 21:44 ` Luis R. Rodriguez
2017-06-24 4:43 ` Greg Kroah-Hartman
2017-07-05 14:59 ` Sumit Semwal
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=CAO_48GFi4TRGDtqo8aPPerpQG5ei+dszrGq_0_t_8A2G-03rvQ@mail.gmail.com \
--to=sumit.semwal@linaro.org \
--cc=computersforpeace@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@kernel.org \
--cc=shuah@kernel.org \
--cc=stable@vger.kernel.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).