From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shahed Shaikh <shshaikh@marvell.com>, dev@dpdk.org
Cc: rmody@marvell.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 1/1] net/bnx2x: fix segfaults due to stale interrupt status
Date: Mon, 25 Feb 2019 14:47:14 +0000 [thread overview]
Message-ID: <4153330d-7820-d659-7b22-5f44f62af1a1@intel.com> (raw)
In-Reply-To: <20190221192444.30575-1-shshaikh@marvell.com>
On 2/21/2019 7:24 PM, Shahed Shaikh wrote:
> Previous ungraceful exit may leave behind un-acked stale
> interrupts for slowpath and fastpath.
>
> Interrupt status polling function is started before FLR is
> initiated, so we don't have a real way to protect this polling
> function invoking an interrupt handler caused due to stale
> interrupt status from previous ungraceful exit.
>
> So, check uninitialized status block variables in interrupt
> handling path which may lead to sefault.
>
> Fixes: 540a211084a7 ("bnx2x: driver core")
> Cc: stable@dpdk.org
>
> Signed-off-by: Shahed Shaikh <shshaikh@marvell.com>
Applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-02-25 14:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 19:24 Shahed Shaikh
2019-02-25 14:47 ` Ferruh Yigit [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=4153330d-7820-d659-7b22-5f44f62af1a1@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=rmody@marvell.com \
--cc=shshaikh@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).