From: "Morten Brørup" <mb@smartsharesystems.com>
To: "Konstantin Ananyev" <konstantin.ananyev@huawei.com>,
"Marat Khalili" <marat.khalili@huawei.com>,
"Christophe Fontaine" <cfontain@redhat.com>
Cc: <dev@dpdk.org>, "Wathsala Vithanage" <wathsala.vithanage@arm.com>
Subject: RE: [PATCH] bpf/arm64: support packet data load instructions
Date: Thu, 19 Mar 2026 10:20:57 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F657A3@smartserver.smartshare.dk> (raw)
In-Reply-To: <78da248e82a54be6882d37efeff23add@huawei.com>
> BTW, I think we still need to add check for overflow in
> __rte_pktmbuf_read() -
> bpf jit is not the only user of it.
> Unless, of-course, we want rte_pktmbuf_read() to work with wrapped-
> around values.
It makes no sense for rte_pktmbuf_read() to wrap around.
Its offset and length parameters are clearly specified and documented as unsigned, and there is no mention of wrap-around or implicit negative values when summing them.
I have submitted a fix just now:
https://inbox.dpdk.org/dev/20260319084048.652493-1-mb@smartsharesystems.com/T/#u
-Morten
next prev parent reply other threads:[~2026-03-19 9:21 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-10 12:20 [PATCH] bpf/arm64: support packet data load instructions Christophe Fontaine
2026-03-17 9:07 ` David Marchand
2026-03-18 11:59 ` Marat Khalili
2026-03-18 12:54 ` Morten Brørup
2026-03-18 13:07 ` Marat Khalili
2026-03-18 13:39 ` Morten Brørup
2026-03-18 15:34 ` Christophe Fontaine
2026-03-18 16:16 ` Marat Khalili
2026-03-18 16:37 ` Morten Brørup
2026-03-18 16:43 ` Marat Khalili
2026-03-18 18:10 ` Konstantin Ananyev
2026-03-19 9:20 ` Morten Brørup [this message]
2026-03-18 23:13 ` Stephen Hemminger
2026-03-19 11:44 ` [PATCH v2 0/2] " Christophe Fontaine
2026-03-19 11:44 ` [PATCH v2 1/2] bpf/arm64: fix offset type to allow a negative jump Christophe Fontaine
2026-03-19 11:44 ` [PATCH v2 2/2] bpf/arm64: support packet data load instructions Christophe Fontaine
2026-03-23 8:15 ` Christophe Fontaine
2026-03-23 9:26 ` Marat Khalili
2026-04-09 22:11 ` Wathsala Vithanage
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=98CBD80474FA8B44BF855DF32C47DC35F657A3@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=cfontain@redhat.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@huawei.com \
--cc=marat.khalili@huawei.com \
--cc=wathsala.vithanage@arm.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