From: Brandon Philips <brandon@ifup.org>
To: postfail@hushmail.com
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-ide@vger.kernel.org
Subject: Re: [PATCH ] /drivers/ata ioremap returncode check
Date: Wed, 22 Aug 2007 11:11:18 -0700 [thread overview]
Message-ID: <20070822181118.GA15764@ifup.org> (raw)
In-Reply-To: <387498.11798.qm@web44905.mail.sp1.yahoo.com>
On 20:31 Mon 13 Aug 2007, Scott Thompson wrote:
> patchset against 2.6.23-rc3. corrects missing ioremap return checks.
>
> Warning -- cleanup handler here may miss additional required cleanup as has occurred on other
> portions of ioremap audit.
>
> This patch had been submitted previously but hushmail client caused wordwrap issues, resending
> with different mail client.
>
> Signed-off-by: Scott Thompson <postfail <at> hushmail.com>
> ----------------------------------------------------------
>
> diff --git a/drivers/ata/pata_ixp4xx_cf.c b/drivers/ata/pata_ixp4xx_cf.c
> index 4ca7fd6..eaebc4d 100644
> --- a/drivers/ata/pata_ixp4xx_cf.c
> +++ b/drivers/ata/pata_ixp4xx_cf.c
> @@ -189,6 +189,14 @@ static __devinit int ixp4xx_pata_probe(struct platform_device *pdev)
> data->cs0 = devm_ioremap(&pdev->dev, cs0->start, 0x1000);
> data->cs1 = devm_ioremap(&pdev->dev, cs1->start, 0x1000);
>
> + if (!data->cs0 || !data->cs1) {
> + if (data->cs0)
> + iounmap(data->cs0);
> + if (data->cs1)
> + iounmap(data->cs1);
> + return -ENOMEM;
> + }
> +
> irq = platform_get_irq(pdev, 0);
> if (irq)
> set_irq_type(irq, IRQT_RISING);
The iounmap calls are unnecessary since devm_ioremap will un-allocate
the space if you return an error from probe. See
Documentation/driver-model/devres.txt
But, something like this is needed.
+ if (!data->cs0 || !data->cs1)
+ return -ENOMEM;
Thanks,
Brandon
parent reply other threads:[~2007-08-22 18:11 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <387498.11798.qm@web44905.mail.sp1.yahoo.com>]
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=20070822181118.GA15764@ifup.org \
--to=brandon@ifup.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=postfail@hushmail.com \
/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).