From: Kees Cook <keescook@chromium.org>
To: Will Deacon <will@kernel.org>
Cc: Keno Fischer <keno@juliacomputing.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Andy Lutomirski <luto@amacapital.net>,
Will Drewry <wad@chromium.org>
Subject: Re: ptrace: seccomp: Return value when the call was already invalid
Date: Fri, 10 Jul 2020 09:14:57 -0700 [thread overview]
Message-ID: <202007100913.B43F8EE371@keescook> (raw)
In-Reply-To: <20200710124253.GB30458@willie-the-truck>
On Fri, Jul 10, 2020 at 01:42:54PM +0100, Will Deacon wrote:
> On Sat, Jul 04, 2020 at 09:56:50PM -0700, Kees Cook wrote:
> > (What doesn't pass for you? I tried to go find kernelci.org test output,
> > but it doesn't appear to actually run selftests yet?)
>
> Sorry, realised I forgot to reply to this point. I was seeing assertion
> failures in 'global.user_notification_with_tsync' and
> 'user_notification_sibling_pid_ns'. I started looking into the first one,
> saw an -EACCESS kicking around, re-ran the tests as root and now they all
> pass.
>
> Are they expected to pass as a normal user?
Oh right, I still have that on my TODO list. Right now the tests are a
mix of root and normal, but since there are some root tests, it needs to
be run as root. I've been meaning to do the appropriate permission tests
and issue SKIPs for the ones needing root..
--
Kees Cook
next prev parent reply other threads:[~2020-07-10 16:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-23 1:01 ptrace: seccomp: Return value when the call was already invalid Keno Fischer
2020-07-03 8:39 ` Will Deacon
2020-07-03 15:17 ` Kees Cook
2020-07-03 15:44 ` Will Deacon
2020-07-03 15:52 ` Kees Cook
2020-07-04 12:33 ` Will Deacon
2020-07-05 4:56 ` Kees Cook
2020-07-06 8:15 ` Will Deacon
2020-07-06 21:40 ` Kees Cook
2020-07-10 12:42 ` Will Deacon
2020-07-10 16:14 ` Kees Cook [this message]
2020-07-03 20:27 ` Keno Fischer
2020-07-04 12:50 ` Will Deacon
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=202007100913.B43F8EE371@keescook \
--to=keescook@chromium.org \
--cc=keno@juliacomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=oleg@redhat.com \
--cc=wad@chromium.org \
--cc=will@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 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.