From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jiri Kosina <jikos@jikos.cz>
Cc: Phil Blundell <philb@gnu.org>, Tim Waugh <tim@cyberelk.net>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, linux-parport@lists.infradead.org
Subject: Re: [PATCH] fix parport_serial_pci_resume() ignoring return value from pci_enable_device()
Date: Fri, 13 Oct 2006 00:58:21 +0100 [thread overview]
Message-ID: <20061012235820.GC24658@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0610130139510.29022@twin.jikos.cz>
On Fri, Oct 13, 2006 at 01:44:24AM +0200, Jiri Kosina wrote:
> (I guess that the parport_serial_pci_remove() is the right way(tm) to
> remove the device from the system in non-destructive way even in case
> pci_enable_device() failed. Tim?)
I suspect all these kind of patches are introducing additional problems.
This one certainly is. Who's auditing all these patches? I mean _properly_
auditing them rather than just saying "that's a good idea"?
In this case, you're calling parport_serial_pci_remove() in the failure
path. That's fine, but this opens the possibility of it being called
twice - once on resume failure and once when the device/driver is
removed. If this happens, we dereference a NULL pointer. *BAD*.
So, the original without this resume fix is probably far better than
with the fix.
So, patch violently rejected.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-10-12 23:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 23:44 [PATCH] fix parport_serial_pci_resume() ignoring return value from pci_enable_device() Jiri Kosina
2006-10-12 23:58 ` Russell King [this message]
2006-10-13 0:03 ` Jiri Kosina
2006-10-13 0:39 ` Jiri Kosina
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=20061012235820.GC24658@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@osdl.org \
--cc=jikos@jikos.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parport@lists.infradead.org \
--cc=philb@gnu.org \
--cc=tim@cyberelk.net \
/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.