DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@mellanox.com>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] net/failsafe: fix Rx interrupt reinstallation
Date: Tue, 13 Feb 2018 22:59:32 +0000	[thread overview]
Message-ID: <1518562772-29823-1-git-send-email-matan@mellanox.com> (raw)

Fail-safe dev_start() operation can be called by both the application
and the hot-plug alarm mechanism.

The installation of Rx interrupt are triggered from dev_start() in any
time it is called while actually the Rx interrupt should be installed
only by the application calls.

So, each plug-in event causes reinstallation which causes memory leak.

Trigger the Rx interrupt installation only for application calls.

Fixes: 9e0360aebf23 ("net/failsafe: register as Rx interrupt mode")

Signed-off-by: Matan Azrad <matan@mellanox.com>
---
 drivers/net/failsafe/failsafe_ops.c | 10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

diff --git a/drivers/net/failsafe/failsafe_ops.c b/drivers/net/failsafe/failsafe_ops.c
index 057e435..bbbd335 100644
--- a/drivers/net/failsafe/failsafe_ops.c
+++ b/drivers/net/failsafe/failsafe_ops.c
@@ -181,10 +181,12 @@
 	int ret;
 
 	fs_lock(dev, 0);
-	ret = failsafe_rx_intr_install(dev);
-	if (ret) {
-		fs_unlock(dev, 0);
-		return ret;
+	if (PRIV(dev)->alarm_lock == 0) {
+		ret = failsafe_rx_intr_install(dev);
+		if (ret) {
+			fs_unlock(dev, 0);
+			return ret;
+		}
 	}
 	FOREACH_SUBDEV(sdev, i, dev) {
 		if (sdev->state != DEV_ACTIVE)
-- 
1.9.5

             reply	other threads:[~2018-02-13 22:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-13 22:59 Matan Azrad [this message]
2018-02-14 13:52 ` Gaëtan Rivet
2018-02-14 13:59   ` Matan Azrad
2018-02-14 14:47 ` [dpdk-dev] [PATCH v2] " Matan Azrad
2018-02-14 15:00   ` Gaëtan Rivet
2018-02-14 15:01     ` Gaëtan Rivet
2018-02-14 15:11       ` Matan Azrad
2018-02-14 15:12       ` Gaëtan Rivet
2018-02-14 15:28     ` 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=1518562772-29823-1-git-send-email-matan@mellanox.com \
    --to=matan@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=gaetan.rivet@6wind.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).