From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Rasesh Mody <rmody@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: Rasesh Mody <rmody@marvell.com>,
"ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 1/3] net/bnx2x: fix read VF id
Date: Tue, 9 Jul 2019 10:33:37 +0000 [thread overview]
Message-ID: <BYAPR18MB24241660C644113FB2AF0C0EC8F10@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190703234313.10782-1-rmody@marvell.com>
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Rasesh Mody
> Sent: Thursday, July 4, 2019 5:13 AM
> To: dev@dpdk.org
> Cc: Rasesh Mody <rmody@marvell.com>; ferruh.yigit@intel.com; GR-
> Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>; stable@dpdk.org
> Subject: [dpdk-dev] [PATCH 1/3] net/bnx2x: fix read VF id
>
> The logic, to read vf_id used by ACQUIRE/TEARDOWN_Q/RELEASE TLVs,
> multiplexed return value to convey vf_id value and status of read vf_id API.
> This lets to segfault at dev_start() as resources are not properly cleaned and
> re-allocated.
>
> Fix read vf_id API to differentiate between vf_id value and return status.
> Adjust the status checking accordingly.
> Added bnx2x_vf_teardown_queue() API and moved relevant code from
> bnx2x_vf_unload() to new API.
>
> Fixes: 540a211084a7 ("bnx2x: driver core")
> Cc: stable@dpdk.org
>
> Signed-off-by: Rasesh Mody <rmody@marvell.com>
Series applied to dpdk-next-net-mrvl/master. Thanks.
prev parent reply other threads:[~2019-07-09 10:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 23:43 Rasesh Mody
2019-07-03 23:43 ` [dpdk-dev] [PATCH 2/3] net/bnx2x: fix link events polling for SRIOV Rasesh Mody
2019-07-03 23:43 ` [dpdk-dev] [PATCH 3/3] net/bnx2x: fix fastpath SB allocation " Rasesh Mody
2019-07-09 10:33 ` Jerin Jacob Kollanukkaran [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=BYAPR18MB24241660C644113FB2AF0C0EC8F10@BYAPR18MB2424.namprd18.prod.outlook.com \
--to=jerinj@marvell.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=rmody@marvell.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).