From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Tiwei Bie <tiwei.bie@intel.com>,
Mohammad Abdul Awal <mohammad.abdul.awal@intel.com>
Cc: dev@dpdk.org, zhihong.wang@intel.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] vhost: fix null pointer checking
Date: Wed, 17 Apr 2019 09:13:17 +0200 [thread overview]
Message-ID: <c0556b40-cf63-7440-320e-4ac097511655@redhat.com> (raw)
Message-ID: <20190417071317.WcMTGJiNjdcFymv24FAIORO5aAxtZf_3VD6uKgP1UFQ@z> (raw)
In-Reply-To: <20190408033845.GC20719@dpdk-tbie.sh.intel.com>
On 4/8/19 5:38 AM, Tiwei Bie wrote:
> On Thu, Apr 04, 2019 at 09:53:17AM +0100, Mohammad Abdul Awal wrote:
>> Null value for parameters will cause segfault.
>>
>> Fixes: d7280c9fff ("vhost: support selective datapath")
>> Fixes: 72e8543093df ("vhost: add API to get MTU value")
>> Fixes: a277c71598 ("vhost: refactor code structure")
>> Fixes: ca33faf9ef ("vhost: introduce API to fetch negotiated features")
>> Fixes: eb32247457 ("vhost: export guest memory regions")
>> Fixes: 40ef286f23 ("vhost: export vhost vring info")
>> Fixes: bd2e0c3fe5 ("vhost: add APIs for live migration")
>> Fixes: 0b8572a0c1 ("vhost: add external message handling to the API")
>> Fixes: b4953225ce ("vhost: add APIs for datapath configuration")
>
> Would be better to use the same length (12) for hashes.
Just FYI, it is possible to define a git alias to do that:
$ git config --get alias.fixline
log -1 --abbrev=12 --format='Fixes: %h ("%s")%nCc: %ae'
$ git fixline c5f21bdae4650bc168638c7b4a2c789e245ba562
Fixes: c5f21bdae465 ("fix indentation in symbol maps")
Cc: thomas@monjalon.net
next prev parent reply other threads:[~2019-04-17 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 8:53 Mohammad Abdul Awal
2019-04-04 8:53 ` Mohammad Abdul Awal
2019-04-08 3:38 ` Tiwei Bie
2019-04-08 3:38 ` Tiwei Bie
2019-04-17 7:13 ` Maxime Coquelin [this message]
2019-04-17 7:13 ` Maxime Coquelin
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=c0556b40-cf63-7440-320e-4ac097511655@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=mohammad.abdul.awal@intel.com \
--cc=stable@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=zhihong.wang@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).