From: Thomas Monjalon <thomas@monjalon.net>
To: Anatoly Burakov <anatoly.burakov@intel.com>
Cc: dev@dpdk.org, keith.wiles@intel.com, herakliusz.lipiec@intel.com,
ferruh.yigit@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] ipc: harden message receive function
Date: Fri, 03 May 2019 14:31:13 +0200 [thread overview]
Message-ID: <14711978.vJqNMZ2rNe@xps> (raw)
Message-ID: <20190503123113.ol7MuV9bKI4YUXKSvMq5mEHdVWAbwNnQCtKMR0Kr2zI@z> (raw)
In-Reply-To: <33816b0f26de3b8328ae49fb6c73ca200acd945b.1556547761.git.anatoly.burakov@intel.com>
29/04/2019 16:22, Anatoly Burakov:
> Currently, IPC does not check received messages for invalid data
> and passes them to user code unchanged. This may result in buffer
> overruns on reading message data. Fix this by checking the message
> length and fd number on receive, and discard any messages that
> are not valid.
>
> Fixes: bacaa2754017 ("eal: add channel for multi-process communication")
> Cc: stable@dpdk.org
>
> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
next prev parent reply other threads:[~2019-05-03 12:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 14:22 Anatoly Burakov
2019-04-29 14:22 ` Anatoly Burakov
2019-05-03 12:31 ` Thomas Monjalon [this message]
2019-05-03 12:31 ` Thomas Monjalon
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=14711978.vJqNMZ2rNe@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=herakliusz.lipiec@intel.com \
--cc=keith.wiles@intel.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).