All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee.jones@linaro.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Dmitry Osipenko <digetx@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mfd: core: Fix double-free in mfd_remove_devices_fn()
Date: Mon, 24 Aug 2020 09:49:35 +0100	[thread overview]
Message-ID: <20200824084935.GJ3248864@dell> (raw)
In-Reply-To: <ac27b0cc-6ede-c7ed-19ee-2472f87f93f7@samsung.com>

On Mon, 24 Aug 2020, Marek Szyprowski wrote:

> Hi
> 
> On 18.08.2020 01:50, Dmitry Osipenko wrote:
> > The pdev.mfd_cell is released by platform_device_release(), which is
> > invoked by platform_device_unregister(). Hence mfd_remove_devices_fn()
> > shouldn't release the cell variable. The double-free bug is reported KASAN
> > during of MFD driver module removal.
> >
> > Fixes: 466a62d7642f ("mfd: core: Make a best effort attempt to match devices with the correct of_nodes")
> > Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
> > ---
> 
> I've reported that almost a week earlier and got information that it 
> will be dropped:
> 
> https://lore.kernel.org/lkml/79bcd1b5-2247-5e00-7d49-2f94f9b40744@samsung.com/
> 
> https://lore.kernel.org/lkml/20200813080100.GI4354@dell/
> 
> Sadly it finally landed in v5.9-rc1. Would be nice to mention this in 
> the revert:

That's true.  The patch was taken out but the change managed to get in
via another commit.  I will add your Reported-by to the revert.

> Reported-by: Marek Szyprowski <m.szyprowski@samsung.com>
> 
> >   drivers/mfd/mfd-core.c | 2 --
> >   1 file changed, 2 deletions(-)
> >
> > diff --git a/drivers/mfd/mfd-core.c b/drivers/mfd/mfd-core.c
> > index c3651f06684f..c50718e3db58 100644
> > --- a/drivers/mfd/mfd-core.c
> > +++ b/drivers/mfd/mfd-core.c
> > @@ -370,8 +370,6 @@ static int mfd_remove_devices_fn(struct device *dev, void *data)
> >   	regulator_bulk_unregister_supply_alias(dev, cell->parent_supplies,
> >   					       cell->num_parent_supplies);
> >   
> > -	kfree(cell);
> > -
> >   	platform_device_unregister(pdev);
> >   	return 0;
> >   }
> 
> Best regards

-- 
Lee Jones [李琼斯]
Senior Technical Lead - Developer Services
Linaro.org │ Open source software for Arm SoCs
Follow Linaro: Facebook | Twitter | Blog

      reply	other threads:[~2020-08-24  9:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20200824083847eucas1p2e5fee0790df8f21934d99e848dc14afe@eucas1p2.samsung.com>
2020-08-17 23:50 ` [PATCH v1] mfd: core: Fix double-free in mfd_remove_devices_fn() Dmitry Osipenko
2020-08-21 14:46   ` Lee Jones
2020-08-24  8:38   ` Marek Szyprowski
2020-08-24  8:49     ` Lee Jones [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=20200824084935.GJ3248864@dell \
    --to=lee.jones@linaro.org \
    --cc=digetx@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.szyprowski@samsung.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 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.