From: Nick Alcock <nix@esperi.org.uk>
To: Kris Van Hees <kris.van.hees@oracle.com>
Cc: dtrace@lists.linux.dev, dtrace-devel@oss.oracle.com
Subject: Re: [PATCH 20/20] test: ensure expected output works for older and newer kernels
Date: Fri, 06 Nov 2026 13:42:11 +0000 [thread overview]
Message-ID: <87ld76qdos.fsf@esperi.org.uk> (raw)
In-Reply-To: <463fcd5adbd3fd710d2579b5873bb6b5@oracle.com>
On 30 Oct 2026, Kris Van Hees told this:
> Older kernel BPF verifiers report -EFAULT whereras newer ones report
> -E2BIG. Support both, and also make the tests more robust if code
> generation might result in a less predictable jump count.
>
> Signed-off-by: Kris Van Hees <kris.van.hees@oracle.com>
Hm, this only seems to be loking for *some* error now, without concern
for what it was. In particulary it's not looking for -E2BIG at all, But
I suppose as long as we're looking for the bpflogsize error message it's
OK.
Reviewed-by: Nick Alcock <nix@esperi.org.uk>
--
NULL && (void)
prev parent reply other threads:[~2026-11-06 13:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 19:37 [PATCH 20/20] test: ensure expected output works for older and newer kernels Kris Van Hees
2026-11-06 13:42 ` Nick Alcock [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=87ld76qdos.fsf@esperi.org.uk \
--to=nix@esperi.org.uk \
--cc=dtrace-devel@oss.oracle.com \
--cc=dtrace@lists.linux.dev \
--cc=kris.van.hees@oracle.com \
/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