public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Dongliang Mu <mudongliangabcd@gmail.com>,
	Pavel Skripkin <paskripkin@gmail.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-media@vger.kernel.org,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>
Subject: Re: Need help in debugging "memory leak in em28xx_init_dev"
Date: Mon, 1 Nov 2021 21:33:01 +0300	[thread overview]
Message-ID: <20211101183301.GF2914@kadam> (raw)
In-Reply-To: <c0e25c48-84cc-6ad1-8312-1957f459148d@infradead.org>

On Mon, Nov 01, 2021 at 08:05:47AM -0700, Randy Dunlap wrote:
> On 11/1/21 7:30 AM, Dan Carpenter 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@gmail.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.
> 
> <20211101095539.423246-1-mudongliangabcd@gmail.com>
> 

Thanks, Randy!

regards,
dan carpenter


      reply	other threads:[~2021-11-01 18:33 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAD-N9QXsUcczurqq9LdaVjXFZMBSbStynwFJyu0UayDazGe=nw@mail.gmail.com>
2021-11-01  7:50 ` Need help in debugging "memory leak in em28xx_init_dev" Pavel Skripkin
2021-11-01  8:55   ` Dongliang Mu
2021-11-01  9:19     ` Pavel Skripkin
2021-11-01  9:41       ` Dongliang Mu
2021-11-01  9:43         ` Pavel Skripkin
2021-11-01  9:58           ` Dongliang Mu
2021-11-01 12:17             ` Pavel Skripkin
2021-11-01 12:23               ` Dongliang Mu
2021-11-01 12:26                 ` Pavel Skripkin
2021-11-01 12:31                   ` Dongliang Mu
2021-11-01 14:30             ` Dan Carpenter
2021-11-01 14:33               ` Dongliang Mu
2021-11-01 15:05               ` Randy Dunlap
2021-11-01 18:33                 ` Dan Carpenter [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=20211101183301.GF2914@kadam \
    --to=dan.carpenter@oracle.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=mudongliangabcd@gmail.com \
    --cc=paskripkin@gmail.com \
    --cc=rdunlap@infradead.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: 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