From: "De Lara Guarch, Pablo" <pablo.de.lara.guarch@intel.com>
To: "Zhang, Roy Fan" <roy.fan.zhang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] crypto/scheduler: fix uninitialized capability structure
Date: Wed, 19 Apr 2017 16:34:04 +0000 [thread overview]
Message-ID: <E115CCD9D858EF4F90C690B0DCB4D8974780CB68@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <9F7182E3F746AB4EA17801C148F3C60409E9AADC@IRSMSX101.ger.corp.intel.com>
> -----Original Message-----
> From: Zhang, Roy Fan
> Sent: Wednesday, April 19, 2017 4:41 PM
> To: De Lara Guarch, Pablo
> Cc: dev@dpdk.org
> Subject: RE: [PATCH] crypto/scheduler: fix uninitialized capability structure
>
> > -----Original Message-----
> > From: De Lara Guarch, Pablo
> > Sent: Wednesday, April 19, 2017 4:02 PM
> > To: Zhang, Roy Fan <roy.fan.zhang@intel.com>
> > Cc: dev@dpdk.org; De Lara Guarch, Pablo
> <pablo.de.lara.guarch@intel.com>
> > Subject: [PATCH] crypto/scheduler: fix uninitialized capability structure
> >
> > Capability information is updated as slaves are attached, but if this
> > information is requested via rte_cryptodev_info_get() when no slaves
> have
> > been attached, the structure would not be initialized, leading to a
> potential
> > segmentation fault.
> >
> > Therefore, the structure should be initialized with no capabilities at device
> > creation.
> >
> > Fixes: 31439ee72b2c ("crypto/scheduler: add API implementations")
> >
> > Signed-off-by: Pablo de Lara <pablo.de.lara.guarch@intel.com>
>
> Acked-by: Fan Zhang <roy.fan.zhang@intel.com>
Applied to dpdk-next-crypto.
Pablo
prev parent reply other threads:[~2017-04-19 16:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-19 15:02 Pablo de Lara
2017-04-19 15:40 ` Zhang, Roy Fan
2017-04-19 16:34 ` De Lara Guarch, Pablo [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=E115CCD9D858EF4F90C690B0DCB4D8974780CB68@IRSMSX108.ger.corp.intel.com \
--to=pablo.de.lara.guarch@intel.com \
--cc=dev@dpdk.org \
--cc=roy.fan.zhang@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).