-
Notifications
You must be signed in to change notification settings - Fork 110
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
xsk: fix destination buffer address when copying with metadata #3950
Conversation
Upstream branch: 07ec7b5 |
d2d4fa2
to
9588f70
Compare
Upstream branch: aa3496a |
2899137
to
28e1922
Compare
9588f70
to
816772e
Compare
Upstream branch: af085f5 |
28e1922
to
a0bcfe7
Compare
816772e
to
5d1b61c
Compare
Upstream branch: db55911 |
a0bcfe7
to
a60be2f
Compare
5d1b61c
to
e869fb9
Compare
Upstream branch: f71b2f6 |
While working on a simplified test for [0] it occurred to me that the following looks fishy: data = xsk_umem__get_data(xsk->umem_area, rx_desc->addr); data_meta = data - sizeof(my metadata); Since the data points to umem frame at addr X, data_mem points to the end of umem frame X-1. I don't think it's by design? 0: https://lore.kernel.org/bpf/20221028181431.05173968@kernel.org/T/#t Cc: Björn Töpel <bjorn@kernel.org> Cc: Magnus Karlsson <magnus.karlsson@intel.com> Cc: Maciej Fijalkowski <maciej.fijalkowski@intel.com> Cc: Jonathan Lemon <jonathan.lemon@gmail.com> Signed-off-by: Stanislav Fomichev <sdf@google.com>
a60be2f
to
463c7ad
Compare
At least one diff in series https://patchwork.kernel.org/project/netdevbpf/list/?series=691907 expired. Closing PR. |
Pull request for series with
subject: xsk: fix destination buffer address when copying with metadata
version: 1
url: https://patchwork.kernel.org/project/netdevbpf/list/?series=691907