From: Kees Cook <keescook@chromium.org>
To: Andrei Vagin <avagin@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/bench/seccomp-notify: don't use assert to check syscall errors
Date: Mon, 3 Jul 2023 12:08:01 -0700 [thread overview]
Message-ID: <202307031207.2F2BFFF9@keescook> (raw)
In-Reply-To: <20230630051953.454638-1-avagin@gmail.com>
On Thu, Jun 29, 2023 at 10:19:53PM -0700, Andrei Vagin wrote:
> Since 616b14b47a86, perf is built with NDEBUG=1 so the macro
> assert() is nop.
>
> Signed-off-by: Andrei Vagin <avagin@gmail.com>
Thanks! I've squashed this onto the patch that introduces the benchmark.
--
Kees Cook
prev parent reply other threads:[~2023-07-03 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-30 5:19 [PATCH] perf/bench/seccomp-notify: don't use assert to check syscall errors Andrei Vagin
2023-07-03 19:08 ` 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=202307031207.2F2BFFF9@keescook \
--to=keescook@chromium.org \
--cc=avagin@gmail.com \
--cc=linux-kernel@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