From: Rene Herman <rene.herman@keyaccess.nl>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Adrian Bunk <bunk@kernel.org>,
ambx1@neo.rr.com, linux-kernel@vger.kernel.org
Subject: Re: pnp_bus_resume(): inconsequent NULL checking
Date: Thu, 21 Feb 2008 06:47:21 +0100 [thread overview]
Message-ID: <47BD1069.1060109@keyaccess.nl> (raw)
In-Reply-To: <200802200959.21814.bjorn.helgaas@hp.com>
On 20-02-08 17:59, Bjorn Helgaas wrote:
> I agree with you that we can just delete the dev->protocol tests
> completely. So I'd rather see something like this (built but untested):
>
>
> PNP: remove dev->protocol NULL checks
>
> Every PNP device should have a valid protocol pointer. If it doesn't,
> something's wrong and we should oops so we can find and fix the problem.
>
> Signed-off-by: Bjorn Helgaas <bjorn.helgaas@hp.com>
Ack from a functional standpoint: we are oopsing in pnp_start/stop_dev
_anyway_ if the protocol pointer isn't set.
Will you coach this upstream? A 2.6.25-rc1 change from me made the coverity
checker pick up on it which might be considered enough of an excuse to call
it a regression and submit this as a fix...
> Index: work6/drivers/pnp/driver.c
> ===================================================================
> --- work6.orig/drivers/pnp/driver.c 2008-02-20 09:46:01.000000000 -0700
> +++ work6/drivers/pnp/driver.c 2008-02-20 09:46:28.000000000 -0700
> @@ -167,7 +167,7 @@
> return error;
> }
>
> - if (pnp_dev->protocol && pnp_dev->protocol->suspend)
> + if (pnp_dev->protocol->suspend)
> pnp_dev->protocol->suspend(pnp_dev, state);
> return 0;
> }
> @@ -181,7 +181,7 @@
> if (!pnp_drv)
> return 0;
>
> - if (pnp_dev->protocol && pnp_dev->protocol->resume)
> + if (pnp_dev->protocol->resume)
> pnp_dev->protocol->resume(pnp_dev);
>
> if (pnp_can_write(pnp_dev)) {
>
Rene.
next prev parent reply other threads:[~2008-02-21 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-19 22:49 pnp_bus_resume(): inconsequent NULL checking Adrian Bunk
2008-02-20 0:00 ` Rene Herman
2008-02-20 16:59 ` Bjorn Helgaas
2008-02-21 5:47 ` Rene Herman [this message]
2008-02-21 15:26 ` Bjorn Helgaas
2008-02-21 16:09 ` Adrian Bunk
2008-02-21 16:18 ` Rene Herman
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=47BD1069.1060109@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=ambx1@neo.rr.com \
--cc=bjorn.helgaas@hp.com \
--cc=bunk@kernel.org \
--cc=linux-kernel@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