From: Kees Cook <keescook@chromium.org>
To: Will Drewry <wad@chromium.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: [PATCH] selftests/seccomp: Flush benchmark output regularly
Date: Thu, 27 May 2021 15:20:27 -0700 [thread overview]
Message-ID: <202105271519.4C8BD290@keescook> (raw)
In-Reply-To: <CAAFS_9GA8UFoN4YYN0cJGXft74op-YaL9H9KvF-FyacLX_qPzg@mail.gmail.com>
On Thu, May 27, 2021 at 02:05:38PM -0500, Will Drewry wrote:
> On Wed, May 26, 2021 at 10:30 PM Kees Cook <keescook@chromium.org> wrote:
> >
> > When running the seccomp benchmark under a test runner, it wouldn't
> > provide any feedback on progress. Force IO flushes during the test.
>
> Would it make sense to just setbuf(stdout, NULL); in main?
*forehead slap* Ugh, yes. That works much better. I will respin. Thank
you for the reminder about setbuf() existing. :)
-Kees
--
Kees Cook
prev parent reply other threads:[~2021-05-27 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 3:30 [PATCH] selftests/seccomp: Flush benchmark output regularly Kees Cook
2021-05-27 19:05 ` Will Drewry
2021-05-27 22:20 ` Kees Cook [this message]
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=202105271519.4C8BD290@keescook \
--to=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=wad@chromium.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