From: "Pai G, Sunil" <sunil.pai.g@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>,
"Laatz, Kevin" <kevin.laatz@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] raw/ioat: fix missing device name in idxd bus scan
Date: Fri, 4 Jun 2021 14:11:15 +0000 [thread overview]
Message-ID: <BYAPR11MB381457E0F0C7308A8628E472BD3B9@BYAPR11MB3814.namprd11.prod.outlook.com> (raw)
In-Reply-To: <YK+scdlrslPKD9v3@bricha3-MOBL.ger.corp.intel.com>
> -----Original Message-----
> From: Richardson, Bruce <bruce.richardson@intel.com>
> Sent: Thursday, May 27, 2021 7:58 PM
> To: Laatz, Kevin <kevin.laatz@intel.com>
> Cc: dev@dpdk.org; stable@dpdk.org; Pai G, Sunil <sunil.pai.g@intel.com>
> Subject: Re: [PATCH] raw/ioat: fix missing device name in idxd bus scan
>
> On Thu, May 27, 2021 at 02:36:09PM +0100, Kevin Laatz wrote:
> > The device name is not being initialized during the idxd bus scan
> > which will cause segmentation faults when an appliation tries to
> > access this information.
> >
> > This patch adds the required initialization of the device name so that
> > it can be read without issues.
> >
> > Fixes: b7aaf417f936 ("raw/ioat: add bus driver for device scanning
> > automatically")
> >
> > Reported-by: Sunil Pai G <sunil.pai.g@intel.com>
> > Signed-off-by: Kevin Laatz <kevin.laatz@intel.com>
> > ---
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
Tested-by: Sunil Pai G <sunil.pai.g@intel.com>
next prev parent reply other threads:[~2021-06-04 14:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 13:36 Kevin Laatz
2021-05-27 14:28 ` Bruce Richardson
2021-06-04 14:11 ` Pai G, Sunil [this message]
2021-06-17 7:21 ` [dpdk-stable] [dpdk-dev] " 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=BYAPR11MB381457E0F0C7308A8628E472BD3B9@BYAPR11MB3814.namprd11.prod.outlook.com \
--to=sunil.pai.g@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=kevin.laatz@intel.com \
--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 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).