[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAD-N9QWifUWfYMW6Q7kBy8VFL2J63mnZj1ktcQfv_KapjEsXZw@mail.gmail.com>
Date: Mon, 1 Nov 2021 22:33:57 +0800
From: Dongliang Mu <mudongliangabcd@...il.com>
To: Dan Carpenter <dan.carpenter@...cle.com>
Cc: Pavel Skripkin <paskripkin@...il.com>,
Mauro Carvalho Chehab <mchehab@...nel.org>,
linux-media@...r.kernel.org,
linux-kernel <linux-kernel@...r.kernel.org>,
Greg KH <gregkh@...uxfoundation.org>
Subject: Re: Need help in debugging "memory leak in em28xx_init_dev"
On Mon, Nov 1, 2021 at 10:30 PM Dan Carpenter <dan.carpenter@...cle.com> wrote:
>
> On Mon, Nov 01, 2021 at 05:58:56PM +0800, Dongliang Mu wrote:
> > On Mon, Nov 1, 2021 at 5:43 PM Pavel Skripkin <paskripkin@...il.com> wrote:
> > >
> > > On 11/1/21 12:41, Dongliang Mu wrote:
> > > >> Hi, Dongliang,
> > > >>
> > > >> Did patch attached to my previous email pass syzbot's reproducer test?
> > > >> Unfortunately, I am not able to test rn :(
> > > >
> > > > Yes, it works. The memory leak does not occur anymore.
> > > >
> > > > But I am crafting another patch based on yours as there is a small
> > > > issue in the retval and I would like to make the error handling code
> > > > uniform.
> > > >
> > >
> > > Cool! Thank you for confirmation.
> >
> > Hi Pavel,
> >
> > Thanks for your advice. I have sent the patch and you are on the CC
> > list. Can you please take a look at and review my patch?
> >
>
> What's the Message-ID of your patch so I can b4 it.
>
> This whole thread has no patches. I don't know why I'm CC'd when the
> only part I'm interested in is not included... :/ Hashtag Grumble.
>
You are back to work already?
I forget to CC you in my `git send-email'. This thread asks for help
as I cannot figure out the root cause of this bug.
> regards,
> dan carpenter
>
Powered by blists - more mailing lists