ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Andy Lutomirski <luto@amacapital.net>
To: Kees Cook <keescook@chromium.org>
Cc: Shuah Khan <shuah.kh@samsung.com>,
	Kevin Hilman <khilman@linaro.org>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Tyler Baker <tyler.baker@linaro.org>,
	Mark Brown <broonie@sirena.org.uk>,
	Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [Ksummit-discuss] [CORE TOPIC] Testing
Date: Tue, 7 Jul 2015 15:02:11 -0700	[thread overview]
Message-ID: <CALCETrUMeOdJstG1djALBidD60xOXNExh5vFZGbUSEJwyzutpw@mail.gmail.com> (raw)
In-Reply-To: <CAGXu5jJN7z0Fa78SmyCe0mWE6mRY5f+giL-8CY_Li3tYwYeZrg@mail.gmail.com>

On Tue, Jul 7, 2015 at 1:46 PM, Kees Cook <keescook@chromium.org> wrote:
> There's also sysctl settings, and we also want privilege level as part
> of that configuration. (i.e. some tests should run as root, some show
> not, etc). It'd be nice to have the tests report these in some
> machine-readable form so that a test harness could check, prepare the
> environment, and then run the tests.
>

There was a fair amount of discussion about machine-readable output at
the last KS.  I don't know whether it ever got implemented.

--Andy

  reply	other threads:[~2015-07-07 22:02 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-07  9:24 Mark Brown
2015-07-07 13:02 ` Alexey Dobriyan
2015-07-07 13:14   ` Mark Brown
2015-07-07 18:47     ` Steven Rostedt
2015-07-07 20:46       ` Kees Cook
2015-07-07 22:02         ` Andy Lutomirski [this message]
2015-07-08 17:37           ` Mark Brown
2015-07-08 10:43       ` Mark Brown
2015-07-09 10:24       ` Masami Hiramatsu
2015-07-09 12:00         ` Steven Rostedt
2015-07-10 10:39         ` Alexey Dobriyan
2015-07-10 14:02           ` Shuah Khan
2015-07-10 14:28             ` Alexey Dobriyan
2015-07-10 15:05             ` Steven Rostedt
2015-07-10 15:54               ` Shuah Khan
2015-07-07 15:25 ` Guenter Roeck
2015-07-07 17:18   ` Mark Brown
2015-07-07 17:23     ` Julia Lawall
2015-07-07 17:24     ` Shuah Khan
2015-07-07 17:37       ` Guenter Roeck
2015-07-07 17:52     ` Guenter Roeck
2015-07-07 18:28       ` Mark Brown
2015-07-07 22:51       ` Peter Hüwe
2015-07-20 15:53     ` Mel Gorman
2015-07-20 16:39       ` Shuah Khan
2015-07-07 19:21   ` Geert Uytterhoeven
2015-07-08  7:54     ` Dan Carpenter
2015-07-08  8:37       ` Geert Uytterhoeven
2015-07-08 12:10         ` Jiri Kosina
2015-07-08 12:37           ` Josh Boyer
2015-07-08 17:32           ` Mark Brown
2015-07-12 10:21         ` Fengguang Wu
2015-07-08  9:52       ` Mark Brown
2015-07-12 11:15         ` Fengguang Wu
2015-07-13 18:34           ` Mark Brown
2015-07-14 14:22             ` Fengguang Wu
2015-07-14 15:38               ` Mark Brown
2015-07-15 14:21                 ` Fengguang Wu
2015-07-08  9:27   ` Michael Ellerman
2015-07-08 13:52     ` Guenter Roeck
2015-07-08 16:40       ` Kevin Hilman
2015-07-08 17:24         ` Guenter Roeck
2015-07-08 18:42           ` Kevin Hilman
2015-07-09  4:23         ` Michael Ellerman
2015-07-09 18:08           ` Guenter Roeck

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=CALCETrUMeOdJstG1djALBidD60xOXNExh5vFZGbUSEJwyzutpw@mail.gmail.com \
    --to=luto@amacapital.net \
    --cc=broonie@sirena.org.uk \
    --cc=dan.carpenter@oracle.com \
    --cc=keescook@chromium.org \
    --cc=khilman@linaro.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=shuah.kh@samsung.com \
    --cc=tyler.baker@linaro.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