linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@zonque.org>
To: sameo@linux.intel.com
Cc: linux-wireless@vger.kernel.org, colin.king@canonical.com,
	shikha.singh@st.com, Daniel Mack <daniel@zonque.org>
Subject: [PATCH v3 07/11] NFC: st95hf: ignore spurious interrupts
Date: Tue, 24 Jul 2018 11:59:37 +0200	[thread overview]
Message-ID: <20180724095941.25777-8-daniel@zonque.org> (raw)
In-Reply-To: <20180724095941.25777-1-daniel@zonque.org>

When an interrupt occurs before st95hf_in_send_cmd() was called, the ISR
will currently dereference a NULL pointer. Fix this by checking whether
`cb_arg->complete_cb' is set, and bail out early if that's not the case.

Again spurious interrupts are likely to occur with EMI noise through the
antenna, and need to be handled gracefully.

Signed-off-by: Daniel Mack <daniel@zonque.org>
---
 drivers/nfc/st95hf/core.c | 19 +++++++++++++++++--
 1 file changed, 17 insertions(+), 2 deletions(-)

diff --git a/drivers/nfc/st95hf/core.c b/drivers/nfc/st95hf/core.c
index 99f84ddfdfef..7fdad67b1a4d 100644
--- a/drivers/nfc/st95hf/core.c
+++ b/drivers/nfc/st95hf/core.c
@@ -796,6 +796,13 @@ static irqreturn_t st95hf_irq_thread_handler(int irq, void  *st95hfcontext)
 		goto end;
 	}
 
+	/*
+	 * If the completion callback is not set, no command is currently
+	 * active. Ignore the spurious interrupt.
+	 */
+	if (unlikely(!cb_arg->complete_cb))
+		goto end;
+
 	/* if stcontext->ddev is %NULL, it means remove already ran */
 	if (!stcontext->ddev) {
 		result = -ENODEV;
@@ -844,8 +851,16 @@ static irqreturn_t st95hf_irq_thread_handler(int irq, void  *st95hfcontext)
 	wtx = false;
 	cb_arg->rats = false;
 	skb_resp = ERR_PTR(result);
-	/* call of callback with error */
-	cb_arg->complete_cb(stcontext->ddev, cb_arg->cb_usrarg, skb_resp);
+
+	/*
+	 * Report an error to the core. If cb_arg->complete_cb is unset,
+	 * we're handling a spurious interrupt that can be ignored.
+	 */
+	if (cb_arg->complete_cb)
+		cb_arg->complete_cb(stcontext->ddev,
+				    cb_arg->cb_usrarg,
+				    skb_resp);
+
 	mutex_unlock(&stcontext->rm_lock);
 	return IRQ_HANDLED;
 }
-- 
2.17.1

  parent reply	other threads:[~2018-07-24 11:05 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24  9:59 [PATCH v3 00/11] NFC: A bunch of cleanups for st95hf Daniel Mack
2018-07-24  9:59 ` [PATCH v3 01/11] Revert "NFC: st95hf: drop illegal kfree_skb()" Daniel Mack
2018-07-24  9:59 ` [PATCH v3 02/11] NFC: st95hf: drop nfcdev_free Daniel Mack
2018-07-24  9:59 ` [PATCH v3 03/11] NFC: st95hf: drop illegal kfree_skb() in IRQ handler Daniel Mack
2018-07-24  9:59 ` [PATCH v3 04/11] NFC: st95hf: remove logging from spi functions Daniel Mack
2018-07-24  9:59 ` [PATCH v3 05/11] NFC: st95hf: remove exchange_lock Daniel Mack
2018-07-24  9:59 ` [PATCH v3 06/11] NFC: st95hf: move skb allocation to ISR Daniel Mack
2018-07-24  9:59 ` Daniel Mack [this message]
2018-07-24  9:59 ` [PATCH v3 08/11] NFC: st95hf: re-order command defines Daniel Mack
2018-07-24  9:59 ` [PATCH v3 09/11] NFC: st95hf: unify sync/async flags Daniel Mack
2018-07-24  9:59 ` [PATCH v3 10/11] NFC: st95hf: two small style nits Daniel Mack
2018-07-24  9:59 ` [PATCH v3 11/11] NFC: st95hf: add of match table Daniel Mack
2018-08-06 10:38 ` [PATCH v3 00/11] NFC: A bunch of cleanups for st95hf Daniel Mack
2018-09-18 10:04   ` Daniel Mack

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=20180724095941.25777-8-daniel@zonque.org \
    --to=daniel@zonque.org \
    --cc=colin.king@canonical.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=shikha.singh@st.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).