All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Andrei Matei <andreimatei1@gmail.com>
Cc: bpf@vger.kernel.org, daniel@iogearbox.net
Subject: Re: [PATCH bpf-next v2] selftest/bpf: testing for multiple logs on REJECT
Date: Wed, 03 Feb 2021 23:30:06 +0000	[thread overview]
Message-ID: <161239500673.24728.11168194942696623869.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210130220150.59305-1-andreimatei1@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Sat, 30 Jan 2021 17:01:50 -0500 you wrote:
> This patch adds support to verifier tests to check for a succession of
> verifier log messages on program load failure. This makes the
> errstr field work uniformly across REJECT and VERBOSE_ACCEPT checks.
> 
> This patch also increases the maximum size of a message in the series of
> messages to test from 80 chars to 200 chars. This is in order to keep
> existing tests working, which sometimes test for messages larger than 80
> chars (which was accepted in the REJECT case, when testing for a single
> message, but not in the VERBOSE_ACCEPT case, when testing for possibly
> multiple messages).
> And example of such a long, checked message is in bounds.c:
> "R1 has unknown scalar with mixed signed bounds, pointer arithmetic with
> it prohibited for !root"
> 
> [...]

Here is the summary with links:
  - [bpf-next,v2] selftest/bpf: testing for multiple logs on REJECT
    https://git.kernel.org/bpf/bpf-next/c/060fd1035880

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2021-02-03 23:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-30 22:01 [PATCH bpf-next v2] selftest/bpf: testing for multiple logs on REJECT Andrei Matei
2021-02-01 23:49 ` Song Liu
2021-02-03 23:30 ` patchwork-bot+netdevbpf [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=161239500673.24728.11168194942696623869.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andreimatei1@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    /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.