From: Guennadi Liakhovetski <g.liakhovetski@gmx.de> To: Chris Ball <cjb@laptop.org> Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org Subject: Re: [PATCH] mmc: sh_mmcif: fix use after free Date: Tue, 30 Oct 2012 22:08:57 +0000 [thread overview] Message-ID: <Pine.LNX.4.64.1210302306190.29432@axis700.grange> (raw) In-Reply-To: <878vapq8fj.fsf@octavius.laptop.org> Hi Chris On Mon, 29 Oct 2012, Chris Ball wrote: > Hi Guennadi, > > On Tue, Oct 23 2012, Guennadi Liakhovetski wrote: > > A recent commit "mmc: sh_mmcif: fix clock management" has introduced a use > > after free bug in sh_mmcif.c: in sh_mmcif_remove() the call to > > mmc_free_host() frees private driver data, therefore using it afterwards > > is a bug. Revert that hunk. > > > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de> > > --- > > > > Chris, the offending patch appeared in 3.6, so, this has to go to > > 3.6.stable, as well as to 3.7-rc. > > > > drivers/mmc/host/sh_mmcif.c | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) > > > > diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c > > index 11d2bc3..d25bc97 100644 > > --- a/drivers/mmc/host/sh_mmcif.c > > +++ b/drivers/mmc/host/sh_mmcif.c > > @@ -1466,9 +1466,9 @@ static int __devexit sh_mmcif_remove(struct platform_device *pdev) > > > > platform_set_drvdata(pdev, NULL); > > > > + clk_disable(host->hclk); > > mmc_free_host(host->mmc); > > pm_runtime_put_sync(&pdev->dev); > > - clk_disable(host->hclk); > > pm_runtime_disable(&pdev->dev); > > > > return 0; > > Thanks, pushed to mmc-next for 3.7. Thanks! > In future, feel free to note the > stable@ situation by adding: > > Cc: stable@vger.kernel.org [3.6] Hm, a bit confused. I seem to remember, that one of subsystem maintainers, to whom I also submitted a patch, that should also have been forwarded to stable, told me, that adding this "Cc: stable@..." tag was a task of subsystem maintainers, in that case his task, and not of individual submitters, which might only indicate their opinion in this respect. Am I wrong? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/
WARNING: multiple messages have this Message-ID (diff)
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de> To: Chris Ball <cjb@laptop.org> Cc: linux-mmc@vger.kernel.org, linux-sh@vger.kernel.org Subject: Re: [PATCH] mmc: sh_mmcif: fix use after free Date: Tue, 30 Oct 2012 23:08:57 +0100 (CET) [thread overview] Message-ID: <Pine.LNX.4.64.1210302306190.29432@axis700.grange> (raw) In-Reply-To: <878vapq8fj.fsf@octavius.laptop.org> Hi Chris On Mon, 29 Oct 2012, Chris Ball wrote: > Hi Guennadi, > > On Tue, Oct 23 2012, Guennadi Liakhovetski wrote: > > A recent commit "mmc: sh_mmcif: fix clock management" has introduced a use > > after free bug in sh_mmcif.c: in sh_mmcif_remove() the call to > > mmc_free_host() frees private driver data, therefore using it afterwards > > is a bug. Revert that hunk. > > > > Signed-off-by: Guennadi Liakhovetski <g.liakhovetski@gmx.de> > > --- > > > > Chris, the offending patch appeared in 3.6, so, this has to go to > > 3.6.stable, as well as to 3.7-rc. > > > > drivers/mmc/host/sh_mmcif.c | 2 +- > > 1 files changed, 1 insertions(+), 1 deletions(-) > > > > diff --git a/drivers/mmc/host/sh_mmcif.c b/drivers/mmc/host/sh_mmcif.c > > index 11d2bc3..d25bc97 100644 > > --- a/drivers/mmc/host/sh_mmcif.c > > +++ b/drivers/mmc/host/sh_mmcif.c > > @@ -1466,9 +1466,9 @@ static int __devexit sh_mmcif_remove(struct platform_device *pdev) > > > > platform_set_drvdata(pdev, NULL); > > > > + clk_disable(host->hclk); > > mmc_free_host(host->mmc); > > pm_runtime_put_sync(&pdev->dev); > > - clk_disable(host->hclk); > > pm_runtime_disable(&pdev->dev); > > > > return 0; > > Thanks, pushed to mmc-next for 3.7. Thanks! > In future, feel free to note the > stable@ situation by adding: > > Cc: stable@vger.kernel.org [3.6] Hm, a bit confused. I seem to remember, that one of subsystem maintainers, to whom I also submitted a patch, that should also have been forwarded to stable, told me, that adding this "Cc: stable@..." tag was a task of subsystem maintainers, in that case his task, and not of individual submitters, which might only indicate their opinion in this respect. Am I wrong? Thanks Guennadi --- Guennadi Liakhovetski, Ph.D. Freelance Open-Source Software Developer http://www.open-technology.de/
next prev parent reply other threads:[~2012-10-30 22:08 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-23 12:08 [PATCH] mmc: sh_mmcif: fix use after free Guennadi Liakhovetski 2012-10-23 12:08 ` Guennadi Liakhovetski 2012-10-29 21:23 ` Chris Ball 2012-10-29 21:23 ` Chris Ball 2012-10-30 22:08 ` Guennadi Liakhovetski [this message] 2012-10-30 22:08 ` Guennadi Liakhovetski 2012-10-30 22:37 ` Chris Ball 2012-10-30 22:37 ` Chris Ball
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=Pine.LNX.4.64.1210302306190.29432@axis700.grange \ --to=g.liakhovetski@gmx.de \ --cc=cjb@laptop.org \ --cc=linux-mmc@vger.kernel.org \ --cc=linux-sh@vger.kernel.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.