From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/3] sdhci-s3c: add missing remove function
Date: Mon, 12 Jul 2010 13:04:09 +0200 [thread overview]
Message-ID: <000201cb21b1$fc69c7f0$f53d57d0$%szyprowski@samsung.com> (raw)
In-Reply-To: <20100709142617.50892f8b.akpm@linux-foundation.org>
Hello,
On Friday, July 09, 2010 11:26 PM Andrew Morton wrote:
> On Wed, 16 Jun 2010 08:49:54 +0200
> Marek Szyprowski <m.szyprowski@samsung.com> wrote:
>
> > Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > ---
> > drivers/mmc/host/sdhci-s3c.c | 20 ++++++++++++++++++++
> > 1 files changed, 20 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/mmc/host/sdhci-s3c.c b/drivers/mmc/host/sdhci-s3c.c
> > index af21792..ad30f07 100644
> > --- a/drivers/mmc/host/sdhci-s3c.c
> > +++ b/drivers/mmc/host/sdhci-s3c.c
> > @@ -365,6 +365,26 @@ static int __devinit sdhci_s3c_probe(struct
> platform_device *pdev)
> >
> > static int __devexit sdhci_s3c_remove(struct platform_device *pdev)
> > {
> > + struct sdhci_host *host = platform_get_drvdata(pdev);
> > + struct sdhci_s3c *sc = sdhci_priv(host);
> > + int ptr;
> > +
> > + sdhci_remove_host(host, 1);
> > +
> > + for (ptr = 0; ptr < 3; ptr++) {
> > + clk_disable(sc->clk_bus[ptr]);
> > + clk_put(sc->clk_bus[ptr]);
> > + }
> > + clk_disable(sc->clk_io);
> > + clk_put(sc->clk_io);
> > +
> > + iounmap(host->ioaddr);
> > + release_resource(sc->ioarea);
> > + kfree(sc->ioarea);
> > +
> > + sdhci_free_host(host);
> > + platform_set_drvdata(pdev, NULL);
> > +
> > return 0;
> > }
>
> This looks like it fixes a pretty serious omission. What happens if
> the user rmmods this driver on a 2.6.34 kernel?
System will crash sooner or later once the memory with the code of the
s3c-sdhci.ko module is reused for something else. I really have no idea
how the lack of remove function went unnoticed into the mainline code.
> Because I have a suspicion that this fix should be backported into
> 2.6.34.x?
Right, this is really a good idea. This patch applies cleanly onto
v2.6.34 too.
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
next prev parent reply other threads:[~2010-07-12 11:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 6:49 [PATCH v2] SDHCI-S3C fixes and enhancements (driver specific code) Marek Szyprowski
2010-06-16 6:49 ` [PATCH 1/3] sdhci-s3c: add missing remove function Marek Szyprowski
2010-07-09 21:26 ` Andrew Morton
2010-07-12 11:04 ` Marek Szyprowski [this message]
2010-07-12 23:52 ` Andrew Morton
2010-06-16 6:49 ` [PATCH 2/3] sdhci-s3c: add support for the non standard minimal clock value Marek Szyprowski
2010-07-09 21:19 ` Andrew Morton
2010-07-12 10:16 ` Marek Szyprowski
2010-06-16 6:49 ` [PATCH 3/3] sdhci-s3c: add support for new card detection methods Marek Szyprowski
2010-07-09 21:24 ` Andrew Morton
2010-07-12 11:04 ` Marek Szyprowski
2010-07-12 12:59 ` [PATCH v3] " Marek Szyprowski
2010-07-06 5:29 ` [PATCH v2] SDHCI-S3C fixes and enhancements (driver specific code) Kyungmin Park
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='000201cb21b1$fc69c7f0$f53d57d0$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).