DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>
Cc: "Kundapura, Ganapati" <ganapati.kundapura@intel.com>,
	"jerinj@marvell.com" <jerinj@marvell.com>,
	 "dev@dpdk.org" <dev@dpdk.org>,
	"Jayatheerthan, Jay" <jay.jayatheerthan@intel.com>,
	 "Gujjar, Abhinandan S" <abhinandan.gujjar@intel.com>
Subject: Re: [PATCH v1] eventdev/eth_rx: fix null pointer dereference
Date: Mon, 28 Aug 2023 21:19:27 +0530	[thread overview]
Message-ID: <CALBAE1Na2HP-QjbU6iG9vm02qqaPxccHG0NjQxHd0Lnk6beW5w@mail.gmail.com> (raw)
In-Reply-To: <DM6PR11MB38682081C2AB451BB5919BA9A1E3A@DM6PR11MB3868.namprd11.prod.outlook.com>

On Fri, Aug 25, 2023 at 7:17 PM Naga Harish K, S V
<s.v.naga.harish.k@intel.com> wrote:
>
>
>
> > -----Original Message-----
> > From: Kundapura, Ganapati <ganapati.kundapura@intel.com>
> > Sent: Thursday, August 24, 2023 1:54 PM
> > To: jerinj@marvell.com; Naga Harish K, S V <s.v.naga.harish.k@intel.com>;
> > dev@dpdk.org
> > Cc: Jayatheerthan, Jay <jay.jayatheerthan@intel.com>; Gujjar, Abhinandan S
> > <abhinandan.gujjar@intel.com>
> > Subject: [PATCH v1] eventdev/eth_rx: fix null pointer dereference
> >
> > On passing NULL as a last parameter to xxx_create_ext_with_params(),
> > rxa_config_params_validate() uses default values and dereferences NULL
> > pointer leading to segmentation fault.
> >
> > Fixed by returning after using default values without dereferencing NULL
> > pointer.
> >
> > Fixes: 8be6c94d6d90 ("eventdev/eth_rx: add new adapter create API")

Squashed to this patch to "8be6c94d6d90 ("eventdev/eth_rx: add new
adapter create API")" and rebase the tree to latest main.

      reply	other threads:[~2023-08-28 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-24  8:23 Ganapati Kundapura
2023-08-25  7:04 ` Jerin Jacob
2023-08-25 13:46 ` Naga Harish K, S V
2023-08-28 15:49   ` Jerin Jacob [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=CALBAE1Na2HP-QjbU6iG9vm02qqaPxccHG0NjQxHd0Lnk6beW5w@mail.gmail.com \
    --to=jerinjacobk@gmail.com \
    --cc=abhinandan.gujjar@intel.com \
    --cc=dev@dpdk.org \
    --cc=ganapati.kundapura@intel.com \
    --cc=jay.jayatheerthan@intel.com \
    --cc=jerinj@marvell.com \
    --cc=s.v.naga.harish.k@intel.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).