linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: <Conor.Dooley@microchip.com>
To: <arnd@arndb.de>, <Nicolas.Ferre@microchip.com>
Cc: <lkp@intel.com>, <kbuild-all@lists.01.org>, <linux-mm@kvack.org>
Subject: Re: [linux-next:master 7918/13392] drivers/soc/microchip/mpfs-sys-controller.c:73:1-6: WARNING: invalid free of devm_ allocated data
Date: Mon, 21 Mar 2022 08:12:35 +0000	[thread overview]
Message-ID: <cd15faf6-6baf-ca97-7157-696bac33aa83@microchip.com> (raw)
In-Reply-To: <3877078c-0797-7742-bd0b-240d1506b4e8@conchuod.ie>

On 18/03/2022 11:59, Conor Dooley wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 18/03/2022 11:02, Arnd Bergmann wrote:
>> On Fri, Mar 18, 2022 at 10:43 AM Nicolas Ferre
>> <nicolas.ferre@microchip.com> wrote:
>>
>>> Is there a drawback to this approach in the sense that it can trigger
>>> other test robots?
>>>
>>> This way, we won't have to disturb Arnd as I believe that his branches
>>> are all ready to be sent to Linus after this week-end. Additional
>>> benefit, you don't have to change your plans and enjoy St Patrick
>>> week-end ;-).
>>
>> I don't mind taking last minute fixes for buggy patches that I have queued
>> up, that seems better than sending the wrong code first and fixing it up
>> later. I would fix it myself, but I don't immediately see what the
>> correct fix it.
>> Do we just remove the kfree(), or does that conflict with the lifetime rules
>> in case we unbind the driver before the put() callback is called?
> 
> I was just going to remove the kfree, but I don't think that's right.
> I'll switch it back to using kzalloc & leave the kfree. I'll send a
> patch later today.

Just to follow up, I sent a fix on Friday:
https://lore.kernel.org/linux-riscv/20220318172107.1599399-1-mail@conchuod.ie/


  reply	other threads:[~2022-03-21  8:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17 18:48 kernel test robot
2022-03-17 21:17 ` conor dooley
2022-03-18  9:42   ` Nicolas Ferre
2022-03-18  9:43   ` Nicolas Ferre
2022-03-18 10:35     ` Conor Dooley
2022-03-18 11:02     ` Arnd Bergmann
2022-03-18 11:59       ` Conor Dooley
2022-03-21  8:12         ` Conor.Dooley [this message]
2022-03-18 12:50       ` Nicolas Ferre

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=cd15faf6-6baf-ca97-7157-696bac33aa83@microchip.com \
    --to=conor.dooley@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=arnd@arndb.de \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox