From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Niels de Vos <niels.devos@wincor-nixdorf.com>
Cc: Andrey Panin <pazke@donpac.ru>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Add support for ITE887x serial chipsets
Date: Tue, 27 Mar 2007 15:17:15 +0100 [thread overview]
Message-ID: <20070327141715.GA20671@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20070327140303.GA11233@deexvs01.wincor-nixdorf.com>
On Tue, Mar 27, 2007 at 04:03:03PM +0200, Niels de Vos wrote:
> +static int __devinit pci_ite887x_init(struct pci_dev *dev)
> +{
> ...
> + if (ret > 0) {
> + dev->dev.driver_data = iobase;
> + } else {
> + /* the device has no UARTs if we get here */
> + release_region(iobase->start, ITE_887x_IOSIZE);
> + }
> +
> + return ret;
> +}
> +
> +static void __devexit pci_ite887x_exit(struct pci_dev *dev)
> +{
> + struct resource *iobase = (struct resource*) dev->dev.driver_data;
> + /* free the private driver data */
> + release_region(iobase->start, ITE_887x_IOSIZE);
> + dev->dev.driver_data = NULL;
> +}
> +
You can't do that. dev->dev.driver_data is used by this very driver
itself to store its own data, or alternatively the parport_serial
driver to store its private data. Therefore, dev->dev.driver_data
will be corrupted between your _init function setting it and your
_exit function using it.
Suggest you read the iobase back from the device to release it.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-03-27 14:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 14:17 [PATCH] Add support for ITE887x serial chipsets Niels de Vos
2007-03-26 20:17 ` Andrey Panin
2007-03-27 14:03 ` Niels de Vos
2007-03-27 14:17 ` Russell King [this message]
2007-03-27 15:54 ` Niels de Vos
2007-03-26 21:14 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2007-03-27 18:30 linux
2007-03-28 9:08 ` Niels de Vos
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=20070327141715.GA20671@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=niels.devos@wincor-nixdorf.com \
--cc=pazke@donpac.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox