From: 0-day Robot <robot@bytheb.org>
To: test-report@dpdk.org
Cc: robot@bytheb.org
Subject: |SUCCESS| pw158284 [RFC] ethdev: fix UAF in rte_eth_tx_burst with filtering
Date: Wed, 29 Oct 2025 20:56:32 -0400 [thread overview]
Message-ID: <20251030005632.2179144-1-robot@bytheb.org> (raw)
In-Reply-To: <20251029235400.1486861-1-stephen@networkplumber.org>
From: robot@bytheb.org
Test-Label: github-robot: build
Test-Status: SUCCESS
http://patchwork.dpdk.org/patch/158284/
_github build: passed_
Build URL: https://github.com/ovsrobot/dpdk/actions/runs/18925765537
next prev parent reply other threads:[~2025-10-30 0:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251029235400.1486861-1-stephen@networkplumber.org>
2025-10-29 23:19 ` qemudev
2025-10-29 23:24 ` qemudev
2025-10-29 23:54 ` checkpatch
2025-10-30 0:27 ` |PENDING| pw158284 [PATCH] [RFC] ethdev: fix UAF in rte_eth_tx_burst dpdklab
2025-10-30 0:27 ` |SUCCESS| " dpdklab
2025-10-30 0:33 ` dpdklab
2025-10-30 0:53 ` dpdklab
2025-10-30 0:54 ` dpdklab
2025-10-30 0:56 ` 0-day Robot [this message]
2025-10-30 0:56 ` |SUCCESS| pw158284 [RFC] ethdev: fix UAF in rte_eth_tx_burst with filtering 0-day Robot
2025-10-30 0:57 ` |PENDING| pw158284 [PATCH] [RFC] ethdev: fix UAF in rte_eth_tx_burst dpdklab
2025-10-30 0:59 ` |SUCCESS| " dpdklab
2025-10-30 1:02 ` |PENDING| " dpdklab
2025-10-30 1:03 ` |SUCCESS| " dpdklab
2025-10-30 1:03 ` dpdklab
2025-10-30 1:12 ` |FAILURE| " dpdklab
2025-10-30 1:27 ` |WARNING| " dpdklab
2025-10-30 1:30 ` |PENDING| " dpdklab
2025-10-30 1:32 ` |SUCCESS| " dpdklab
2025-10-30 1:42 ` |WARNING| " dpdklab
2025-10-30 1:51 ` |SUCCESS| " dpdklab
2025-10-30 1:54 ` dpdklab
2025-10-30 1:56 ` |WARNING| " dpdklab
2025-10-30 2:01 ` dpdklab
2025-10-30 2:02 ` |SUCCESS| " dpdklab
2025-10-30 7:51 ` dpdklab
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=20251030005632.2179144-1-robot@bytheb.org \
--to=robot@bytheb.org \
--cc=test-report@dpdk.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;
as well as URLs for NNTP newsgroup(s).