linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Conor Dooley <conor.dooley@microchip.com>,
	kbuild test robot <lkp@intel.com>, <kbuild-all@lists.01.org>,
	Linux-MM <linux-mm@kvack.org>, conor dooley <mail@conchuod.ie>
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: Fri, 18 Mar 2022 13:50:38 +0100	[thread overview]
Message-ID: <4d80ae1a-412d-3b86-6cfd-f457736c1e42@microchip.com> (raw)
In-Reply-To: <CAK8P3a1Hju45+Moji3zPpgegxLoPVR2gFa0P3AixQQoQPA-ebQ@mail.gmail.com>

On 18/03/2022 at 12:02, Arnd Bergmann wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> 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.

Fair enough.

> 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?

Thanks Arnd! Best regards,
   Nicolas


-- 
Nicolas Ferre


      parent reply	other threads:[~2022-03-18 12:50 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
2022-03-18 12:50       ` Nicolas Ferre [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=4d80ae1a-412d-3b86-6cfd-f457736c1e42@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=arnd@arndb.de \
    --cc=conor.dooley@microchip.com \
    --cc=kbuild-all@lists.01.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@intel.com \
    --cc=mail@conchuod.ie \
    /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