From: Patrick Robb <probb@iol.unh.edu>
To: Mihai Brodschi <mihai.brodschi@broadcom.com>
Cc: Jakub Grajciar <jgrajcia@cisco.com>,
Ferruh Yigit <ferruh.yigit@amd.com>,
dev@dpdk.org, stable@dpdk.org
Subject: Re: [PATCH v2] net/memif: fix buffer overflow in zero copy Rx
Date: Mon, 1 Jul 2024 00:57:28 -0400 [thread overview]
Message-ID: <CAJvnSUD0MP-YNQUKXdJcyqzY80ZM8kKmoPro5ZQABRGjqz_iFA@mail.gmail.com> (raw)
In-Reply-To: <c3a72bcb-24b0-4c42-9a07-427eadce029a@broadcom.com>
I see this patchseries had a CI testing fail, for coremask DTS test on
Marvel CN10k. I don't think it could relate to the contents of your
patch though.
It had a timeout:
TestCoremask: Test Case test_individual_coremask Result FAILED:
TIMEOUT on ./arm64-native-linuxapp-gcc/app/test/dpdk-test -c 0x8000
-n 2 --log-level="lib.eal,8"
So, I'm issuing a retest.
Recheck-request: iol-marvell-Functional
prev parent reply other threads:[~2024-07-01 4:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-28 21:01 Mihai Brodschi
2024-07-01 4:57 ` Patrick Robb [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=CAJvnSUD0MP-YNQUKXdJcyqzY80ZM8kKmoPro5ZQABRGjqz_iFA@mail.gmail.com \
--to=probb@iol.unh.edu \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jgrajcia@cisco.com \
--cc=mihai.brodschi@broadcom.com \
--cc=stable@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).