linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Wei Yongjun <weiyj.lk@gmail.com>
Cc: lauro.venancio@openbossa.org, aloisio.almeida@openbossa.org,
	sameo@linux.intel.com, yongjun_wei@trendmicro.com.cn,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH v2] NFC: pn544_hci: move the dereference below the NULL test
Date: Sat, 08 Sep 2012 07:37:45 -0500	[thread overview]
Message-ID: <504B3C19.5040405@lwfinger.net> (raw)
In-Reply-To: <CAPgLHd-DabDrNN9KpQjG+XiXJDA38_VA2jeiF+O-7QBqNhEogA@mail.gmail.com>

On 09/07/2012 10:34 PM, Wei Yongjun wrote:
> On 09/08/2012 10:03 AM, Larry Finger wrote:
>> On 09/07/2012 08:53 PM, Wei Yongjun wrote:
>>> From: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>>>
>>> The dereference should be moved below the NULL test.
>>>
>>> spatch with a semantic match is used to found this.
>>> (http://coccinelle.lip6.fr/)
>>>
>>> Signed-off-by: Wei Yongjun <yongjun_wei@trendmicro.com.cn>
>>> ---
>>>
>>
>> As long as you are reworking this section, doesn't BUG_ON seem a little harsh? I do not think the kernel should ever be crashed because a non-essential driver is messed up. As the patch would be a totally different change, it should be a new submission, but I think each of these conditions should trigger a WARN_ON_ONCE, and return IRQ_NONE when they occur.
>>
> You means the should be like this?
>
> diff --git a/drivers/nfc/pn544_hci.c b/drivers/nfc/pn544_hci.c
> index aa71807..e42b100 100644
> --- a/drivers/nfc/pn544_hci.c
> +++ b/drivers/nfc/pn544_hci.c
> @@ -341,13 +341,16 @@ flush:
>   static irqreturn_t pn544_hci_irq_thread_fn(int irq, void *dev_id)
>   {
>   	struct pn544_hci_info *info = dev_id;
> -	struct i2c_client *client = info->i2c_dev;
> +	struct i2c_client *client;
>   	struct sk_buff *skb = NULL;
>   	int r;
>
> -	BUG_ON(!info);
> -	BUG_ON(irq != info->i2c_dev->irq);
> +	if (!info || irq != info->i2c_dev->irq) {
> +		WARN_ON_ONCE(1);
> +		return IRQ_NONE;
> +	}
>
> +	client = info->i2c_dev;
>   	dev_dbg(&client->dev, "IRQ\n");
>
>   	if (info->hard_fault != 0)

Yes, that looks better to me.

Larry



  reply	other threads:[~2012-09-08 12:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-08  3:34 [PATCH v2] NFC: pn544_hci: move the dereference below the NULL test Wei Yongjun
2012-09-08 12:37 ` Larry Finger [this message]
2012-09-10 13:10 ` Kalle Valo
  -- strict thread matches above, loose matches on Subject: below --
2012-09-08  1:53 Wei Yongjun
2012-09-08  2:03 ` Larry Finger

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=504B3C19.5040405@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=aloisio.almeida@openbossa.org \
    --cc=lauro.venancio@openbossa.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    --cc=weiyj.lk@gmail.com \
    --cc=yongjun_wei@trendmicro.com.cn \
    /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).