All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arvid Brodin <arvid.brodin@enea.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: Memory leak in isp1760-hcd.c
Date: Mon, 24 Oct 2011 14:50:19 +0200	[thread overview]
Message-ID: <4EA55F0B.1070906@enea.com> (raw)
In-Reply-To: <20111019152132.GH29653@arm.com>

Hi, and sorry for the late reply.

Catalin Marinas wrote:
> Hi Arvid,
> 
> I get the following kmemleak report coming from the ISP1760 driver:
> 
*snip*
> 
> Is there a race condition between isp1760_endpoint_disable and
> isp1760_irq?
 
Yes, I think there is. Thanks for a great bug report!

Please try the patches in following emails.

-- 
Arvid Brodin
Enea Services Stockholm AB

  parent reply	other threads:[~2011-10-24 12:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-19 15:21 Memory leak in isp1760-hcd.c Catalin Marinas
2011-10-19 15:42 ` Catalin Marinas
2011-10-24 12:50 ` Arvid Brodin [this message]
2011-10-24 13:11   ` Catalin Marinas
2011-10-24 13:46     ` Arvid Brodin
2011-10-24 12:53 ` Memory leak in isp1760-hcd.c - [PATCH 2/2] usb/isp1760: Fix race condition memory leak Arvid Brodin

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=4EA55F0B.1070906@enea.com \
    --to=arvid.brodin@enea.com \
    --cc=catalin.marinas@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 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.