From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] net: hisilicon: unmap IO resources when cleanup
Date: Sat, 29 Nov 2014 19:54:08 +0100 [thread overview]
Message-ID: <4355983.Q40FtqNjx8@wuerfel> (raw)
In-Reply-To: <5479345A.20408@gmail.com>
On Saturday 29 November 2014 10:50:02 Orson Zhai wrote:
> On 2014?11?29? 09:48, Sheng Yong wrote:
> > Unmap IO resources if the driver initailization failed or the driver is
> > unmounted.
> >
> > Signed-off-by: Sheng Yong <shengyong1@huawei.com>
> > ---
> > drivers/net/ethernet/hisilicon/hix5hd2_gmac.c | 14 ++++++++++----
> > 1 file changed, 10 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/net/ethernet/hisilicon/hix5hd2_gmac.c b/drivers/net/ethernet/hisilicon/hix5hd2_gmac.c
> > index 0ffdcd3..3399ce6 100644
> > --- a/drivers/net/ethernet/hisilicon/hix5hd2_gmac.c
> > +++ b/drivers/net/ethernet/hisilicon/hix5hd2_gmac.c
> > @@ -917,26 +917,26 @@ static int hix5hd2_dev_probe(struct platform_device *pdev)
> > priv->ctrl_base = devm_ioremap_resource(dev, res);
> > if (IS_ERR(priv->ctrl_base)) {
> > ret = PTR_ERR(priv->ctrl_base);
> > - goto out_free_netdev;
> > + goto out_base;
> As i know we don't need to do anything but return error code from probe
> when using devm_xxx for getting resource.
> What's the idea to io-unmap explicitly here?
>
I think it's actually a bug to pair devm_ioremap() with iounmap,
since the iounmap will be done twice then, and that causes
undefined behavior.
In cases where you have to unmap something explicitly, devm_iounmap
should be used, but in this case the patch seems entirely wrong,
the code without the patch looks correct.
Arnd
prev parent reply other threads:[~2014-11-29 18:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 1:48 [PATCH] net: hisilicon: unmap IO resources when cleanup Sheng Yong
2014-11-29 2:50 ` Orson Zhai
2014-11-29 18:54 ` Arnd Bergmann [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=4355983.Q40FtqNjx8@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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