From: Thomas Monjalon <thomas@monjalon.net>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>,
Yangchao Zhou <zhouyates@gmail.com>
Subject: Re: [dpdk-dev] [PATCH] kni: fix possible buffer overflow
Date: Thu, 18 Jul 2019 23:35:33 +0200 [thread overview]
Message-ID: <3307247.H1C8Hm2GdE@xps> (raw)
In-Reply-To: <1846983.CBm7lp9OS6@xps>
18/07/2019 23:24, Thomas Monjalon:
> 11/07/2019 17:33, Stephen Hemminger:
> > On Thu, 11 Jul 2019 13:35:07 +0100
> > Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> >
> > > 'kni_net_rx_lo_fifo()' can get segmented buffers, using 'pkt_len' for
> > > that case will be wrong and some values can cause buffer overflow
> > > in destination mbuf data.
> > >
> > > Signed-off-by: Ferruh Yigit <ferruh.yigit@intel.com>
> >
> > Acked-by: Stephen Hemminger <stephen@networkplumber.org>
>
> Applied, thanks
I hope these lines are correct:
Fixes: d89a58dfe90b ("kni: support chained mbufs")
Cc: stable@dpdk.org
next prev parent reply other threads:[~2019-07-18 21:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 12:35 Ferruh Yigit
2019-07-11 15:33 ` Stephen Hemminger
2019-07-18 21:24 ` Thomas Monjalon
2019-07-18 21:35 ` Thomas Monjalon [this message]
2019-07-19 18:34 ` Ferruh Yigit
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=3307247.H1C8Hm2GdE@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.org \
--cc=zhouyates@gmail.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;
as well as URLs for NNTP newsgroup(s).