On Mon, 12 Jul 2010 13:04:09 +0200
Marek Szyprowski <m.szyprowski@xxxxxxxxxxx> wrote:
> > > 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.
OK, thanks, I added the Cc: <stable@xxxxxxxxxx> to the changelog and
moved the patch into my for-2.6.35 queue.
--
To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
