All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com>, dev@dpdk.org
Cc: stable@dpdk.org
Subject: Re: [PATCH v2] memory: fix segfault on rte_mem_virt2memseg() call with invalid addr
Date: Fri, 1 Jun 2018 15:58:05 +0100	[thread overview]
Message-ID: <3d4f9187-7342-46bc-d598-99c7fe35d725@intel.com> (raw)
In-Reply-To: <1527860679-110206-1-git-send-email-dariuszx.stojaczyk@intel.com>

On 01-Jun-18 2:44 PM, Dariusz Stojaczyk wrote:
> When trying to use it with an address that's not
> managed by DPDK it would segfault due to a missing
> check. The doc says this function returns either
> a pointer or NULL, so let it do so.
> 
> Changes from v1:
>   * removed gerrit change id
>   * added "git fixline" tags
> 
> Fixes: 66cc45e293ed ("mem: replace memseg with memseg lists")
> Cc: anatoly.burakov@intel.com
> Cc: stable@dpdk.org
> 
> Signed-off-by: Dariusz Stojaczyk <dariuszx.stojaczyk@intel.com>
> ---

Please include Acks (Reviews, Tests...) in the commit message if they 
were given for the previous version of the patchset. Also do not list 
changes you've made in the commit message; instead, list changes in the 
patch notes, after the first "---", like so:

area: fix blah

This patch fixes this and that.

Fixes: 123456 ("area: a buggy commit")
Cc: bug.author@example.com

Signed-off-by: Fix Author <fix.author@example.com>
Acked-by: fix.reviewer@example.com

---

v2:
- Fixed this
- Fixed that

-- 
Thanks,
Anatoly

  reply	other threads:[~2018-06-01 14:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-01 13:22 [PATCH] memory: fix segfault on rte_mem_virt2memseg() call with invalid addr Dariusz Stojaczyk
2018-06-01 10:50 ` Burakov, Anatoly
2018-06-01 13:44 ` [PATCH v2] " Dariusz Stojaczyk
2018-06-01 14:58   ` Burakov, Anatoly [this message]
2018-06-04  5:33   ` [PATCH v3] " Dariusz Stojaczyk
2018-07-12 21:44     ` [dpdk-stable] " 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=3d4f9187-7342-46bc-d598-99c7fe35d725@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=dariuszx.stojaczyk@intel.com \
    --cc=dev@dpdk.org \
    --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 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.