From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Joyce Kong <joyce.kong@arm.com>, Jakub Grajciar <jgrajcia@cisco.com>
Cc: <dev@dpdk.org>, <nd@arm.com>, <stable@dpdk.org>,
Ruifeng Wang <ruifeng.wang@arm.com>
Subject: Re: [PATCH] net/memif: fix overwriting of head segment
Date: Wed, 25 May 2022 22:14:25 +0100 [thread overview]
Message-ID: <1b7c4198-01fe-2fa5-e5ee-3e750b4e1bcb@xilinx.com> (raw)
In-Reply-To: <20220525055635.308716-1-joyce.kong@arm.com>
On 5/25/2022 6:56 AM, Joyce Kong wrote:
> The 'dst_off' was reset in multi segment case.
> This caused memif buffer segment to write to
> beginning of mbuf, overwriting previous data.
> Fix it with this patch.
>
> Fixes: 09c7e63a71f9 ("net/memif: introduce memory interface PMD")
> Cc:stable@dpdk.org
>
> Reported-by: Ferruh Yigit<ferruh.yigit@xilinx.com>
> Signed-off-by: Joyce Kong<joyce.kong@arm.com>
> Reviewed-by: Ruifeng Wang<ruifeng.wang@arm.com>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2022-05-25 21:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 5:56 Joyce Kong
2022-05-25 21:14 ` Ferruh Yigit [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=1b7c4198-01fe-2fa5-e5ee-3e750b4e1bcb@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=dev@dpdk.org \
--cc=jgrajcia@cisco.com \
--cc=joyce.kong@arm.com \
--cc=nd@arm.com \
--cc=ruifeng.wang@arm.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).