patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Jiang, Cheng1" <cheng1.jiang@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: Maxime Coquelin <maxime.coquelin@redhat.com>,
	"Xia, Chenbo" <chenbo.xia@intel.com>, dev <dev@dpdk.org>,
	dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] examples/vhost: fix potential overflow in args process
Date: Tue, 27 Apr 2021 03:17:12 +0000
Message-ID: <SJ0PR11MB500697BBEC786C17567D2319DC419@SJ0PR11MB5006.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8z8BmPFr0rhEmtgfMFfEjjSLimLUsthVdogqPs3gJW4aw@mail.gmail.com>

Hi,

> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Monday, April 26, 2021 4:25 PM
> To: Jiang, Cheng1 <cheng1.jiang@intel.com>
> Cc: Maxime Coquelin <maxime.coquelin@redhat.com>; Xia, Chenbo
> <chenbo.xia@intel.com>; dev <dev@dpdk.org>; dpdk stable
> <stable@dpdk.org>
> Subject: Re: [dpdk-stable] [PATCH] examples/vhost: fix potential overflow in
> args process
> 
> On Mon, Apr 19, 2021 at 7:59 AM Cheng Jiang <Cheng1.jiang@intel.com>
> wrote:
> >
> > Add args length check to fix potential overflow issue.
> >
> > Coverity issue: 363741
> > Fixes: 965b06f0358 ("examples/vhost: enhance getopt_long usage")
> > Cc: stable@dpdk.org
> 
> No need for Cc: stable since this issue only affects the current release.

Sure, sorry about that.

> 
> >
> > Signed-off-by: Cheng Jiang <Cheng1.jiang@intel.com>
> 
> It should indeed fix the coverity report but this limit does not make sense.
> Could you make dma_type point at either optarg (it should be fine as
> we only read this string)?
> 
> Something like (untested):
> 
> diff --git a/examples/vhost/main.c b/examples/vhost/main.c
> index 2ca7d98c58..158e5e9a8a 100644
> --- a/examples/vhost/main.c
> +++ b/examples/vhost/main.c
> @@ -55,9 +55,6 @@
> 
>  #define INVALID_PORT_ID 0xFF
> 
> -/* Maximum long option length for option parsing. */
> -#define MAX_LONG_OPT_SZ 64
> -
>  /* mask of enabled ports */
>  static uint32_t enabled_port_mask = 0;
> 
> @@ -97,7 +94,7 @@ static int builtin_net_driver;
> 
>  static int async_vhost_driver;
> 
> -static char dma_type[MAX_LONG_OPT_SZ];
> +static char *dma_type;
> 
>  /* Specify timeout (in useconds) between retries on RX. */
>  static uint32_t burst_rx_delay_time = BURST_RX_WAIT_US;
> @@ -201,7 +198,7 @@ struct vhost_bufftable
> *vhost_txbuff[RTE_MAX_LCORE
> * MAX_VHOST_DEVICE];
>  static inline int
>  open_dma(const char *value)
>  {
> -       if (strncmp(dma_type, "ioat", 4) == 0)
> +       if (dma_type != NULL && strncmp(dma_type, "ioat", 4) == 0)
>                 return open_ioat(value);
> 
>         return -1;
> @@ -669,7 +666,7 @@ us_vhost_parse_args(int argc, char **argv)
>                         break;
> 
>                 case OPT_DMA_TYPE_NUM:
> -                       strcpy(dma_type, optarg);
> +                       dma_type = optarg;
>                         break;
> 
>                 case OPT_DMAS_NUM:
> @@ -1472,7 +1469,7 @@ new_device(int vid)
>                 struct rte_vhost_async_features f;
>                 struct rte_vhost_async_channel_ops channel_ops;
> 
> -               if (strncmp(dma_type, "ioat", 4) == 0) {
> +               if (dma_type != NULL && strncmp(dma_type, "ioat", 4) == 0) {
>                         channel_ops.transfer_data = ioat_transfer_data_cb;
>                         channel_ops.check_completed_copies =
>                                 ioat_check_completed_copies_cb;
> 
> 
> 
> --
> David Marchand

I think that make sense. I'll send a new version according your comments.

Thanks.
Cheng

      reply	other threads:[~2021-04-27  3:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-19  5:44 Cheng Jiang
2021-04-26  8:24 ` David Marchand
2021-04-27  3:17   ` Jiang, Cheng1 [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=SJ0PR11MB500697BBEC786C17567D2319DC419@SJ0PR11MB5006.namprd11.prod.outlook.com \
    --to=cheng1.jiang@intel.com \
    --cc=chenbo.xia@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=maxime.coquelin@redhat.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

patches for DPDK stable branches

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/stable/0 stable/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 stable stable/ https://inbox.dpdk.org/stable \
		stable@dpdk.org
	public-inbox-index stable

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.stable


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git