From: Marc Kleine-Budde <mkl@pengutronix.de>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-can@vger.kernel.org,
AnilKumar Ch <anilkumar@ti.com>,
Marc Kleine-Budde <mkl@pengutronix.de>
Subject: [PATCH 3/4] can: c_can: fix race condition in c_can_open()
Date: Mon, 4 Jun 2012 00:21:59 +0200 [thread overview]
Message-ID: <1338762120-12695-4-git-send-email-mkl@pengutronix.de> (raw)
In-Reply-To: <1338762120-12695-1-git-send-email-mkl@pengutronix.de>
From: AnilKumar Ch <anilkumar@ti.com>
Fix the issue of C_CAN interrupts getting disabled forever when canconfig
utility is used multiple times. According to NAPI usage we disable all
the hardware interrupts in ISR and re-enable them in poll(). Current
implementation calls napi_enable() after hardware interrupts are enabled.
If we get any interrupts between these two steps then we do not process
those interrupts because napi is not enabled. Mostly these interrupts
come because of STATUS is not 0x7 or ERROR interrupts. If napi_enable()
happens before HW interrupts enabled then c_can_poll() function will be
called eventual re-enabling.
This patch moves the napi_enable() call before interrupts enabled.
Cc: stable@kernel.org # 2.6.39+
Signed-off-by: AnilKumar Ch <anilkumar@ti.com>
Acked-by: Wolfgang Grandegger <wg@grandegger.com>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
---
drivers/net/can/c_can/c_can.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/drivers/net/can/c_can/c_can.c b/drivers/net/can/c_can/c_can.c
index fa01621..8dc84d6 100644
--- a/drivers/net/can/c_can/c_can.c
+++ b/drivers/net/can/c_can/c_can.c
@@ -1064,10 +1064,11 @@ static int c_can_open(struct net_device *dev)
goto exit_irq_fail;
}
+ napi_enable(&priv->napi);
+
/* start the c_can controller */
c_can_start(dev);
- napi_enable(&priv->napi);
netif_start_queue(dev);
return 0;
--
1.7.4.1
next prev parent reply other threads:[~2012-06-03 22:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-03 22:21 pull-request: can 2012-06-03 Marc Kleine-Budde
2012-06-03 22:21 ` [PATCH 1/4] can: c_can: fix "BUG! echo_skb is occupied!" during transmit Marc Kleine-Budde
2012-06-03 22:21 ` [PATCH 2/4] can: c_can: fix an interrupt thrash issue with c_can driver Marc Kleine-Budde
2012-06-03 22:21 ` Marc Kleine-Budde [this message]
2012-06-03 22:22 ` [PATCH 4/4] can: cc770: Fix likely misuse of | for & Marc Kleine-Budde
2012-06-04 15:44 ` pull-request: can 2012-06-03 David Miller
2012-06-04 15:46 ` Marc Kleine-Budde
2012-06-04 15:51 ` David Miller
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=1338762120-12695-4-git-send-email-mkl@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=anilkumar@ti.com \
--cc=davem@davemloft.net \
--cc=linux-can@vger.kernel.org \
--cc=netdev@vger.kernel.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).