From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Alexander Strakh <strakh@ispras.ru>,
Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>,
Donald Becker <becker@scyld.com>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 3c507.c: remove unused NULL pointer check
Date: Mon, 21 Dec 2009 21:46:23 +0100 [thread overview]
Message-ID: <4B2FDE9F.1070108@hartkopp.net> (raw)
In-Reply-To: <20091221123111.4498b17c@nehalam>
Stephen Hemminger wrote:
> On Mon, 21 Dec 2009 17:56:39 +0100
> Oliver Hartkopp <socketcan@hartkopp.net> wrote:
>
>> Alexander Strakh wrote:
>>> In driver drivers/net/3c507.c in function Iirqreturn_t el16_interrupt:
>>> 1. If in line 555 dev = NULL then we goto line 556
>>> 2. In line 556 we have null dereference because pr_err called with dev->name
>>> in third parameter.
>>> 555 if (dev == NULL) {
>>> 556 pr_err("%s: net_interrupt(): irq %d for unknown device.
>>> \n",
>>> 557 dev->name, irq);
>>> 558 return IRQ_NONE;
>>> 559 }
>>>
>>> Found by Linux Device Drivers Verification (Svace detector)
>>>
>>> Remove unused NULL pointer check.
>
> Interrupts will never be called with third parameter of NULL. It is really
> bogus impossible to reach code.
>
You're right! I just did not verify the direct assignment of dev = dev_id ...
Btw. the description for the reason of this patch remains unsuitably as the
problem is not the potential dereferencing of dev->name in pr_err() here.
It should better be something like this (partly stolen from your answer):
Interrupts will never be called with dev_id parameter of NULL.
This patch removes the obsolete, unreachable code.
Regards,
Oliver
prev parent reply other threads:[~2009-12-21 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 19:23 [PATCH] 3c507.c: remove unused NULL pointer check Alexander Strakh
2009-12-21 16:56 ` Oliver Hartkopp
2009-12-21 20:31 ` Stephen Hemminger
2009-12-21 20:46 ` Oliver Hartkopp [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=4B2FDE9F.1070108@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=becker@scyld.com \
--cc=bzolnier@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=strakh@ispras.ru \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.