All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Shreyansh Jain <shreyansh.jain@nxp.com>
Cc: Olivier Matz <olivier.matz@6wind.com>,
	dev@dpdk.org, hemant.agrawal@nxp.com, david.hunt@intel.com
Subject: Re: [PATCH v3 1/3] mempool: fix segfault when shared mempool handler not linked
Date: Mon, 03 Apr 2017 18:58:32 +0200	[thread overview]
Message-ID: <2791910.qOPMfRUke8@xps13> (raw)
In-Reply-To: <20170331154924.3e6e117d@platinum>

2017-03-31 15:49, Olivier Matz:
> On Fri, 31 Mar 2017 11:05:35 +0530, Shreyansh Jain <shreyansh.jain@nxp.com> wrote:
> > Fixes: 449c49b93a6b ("mempool: support handler operations")
> > 
> > In case the stack or ring mempool handler are compiled as shared
> > library and not linked in with test binary, segfault is reported.
> > This is because return value of rte_mempool_set_ops_byname is not
> > being checked in rte_mempool_ops_alloc.
> > 
> > This patch handles error returned from rte_mempool_set_ops_byname
> > when a mempool is not found.
> > 
> > Signed-off-by: Shreyansh Jain <shreyansh.jain@nxp.com>
> 
> Acked-by: Olivier Matz <olivier.matz@6wind.com>

Series applied, thanks

      reply	other threads:[~2017-04-03 16:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11490938158-936-1-git-send-email-shreyansh.jain@nxp.com>
2017-03-31  5:35 ` [PATCH v3 1/3] mempool: fix segfault when shared mempool handler not linked Shreyansh Jain
2017-03-31  5:35   ` [PATCH v3 2/3] mempool: introduce ring mempool driver Shreyansh Jain
2017-03-31 13:49     ` Olivier Matz
2017-03-31  5:35   ` [PATCH v3 3/3] mempool: introduce stack " Shreyansh Jain
2017-03-31 13:50     ` Olivier Matz
2017-03-31  5:41   ` [PATCH v3 1/3] mempool: fix segfault when shared mempool handler not linked Shreyansh Jain
2017-03-31 13:44     ` Olivier Matz
2017-03-31 13:49   ` Olivier Matz
2017-04-03 16:58     ` Thomas Monjalon [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=2791910.qOPMfRUke8@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=hemant.agrawal@nxp.com \
    --cc=olivier.matz@6wind.com \
    --cc=shreyansh.jain@nxp.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.