linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Gunnar Larisch <Gunnar.Larisch@softing.com>,
	<linuxppc-dev@lists.linuxppc.org>
Cc: <wd@denx.de>
Subject: Re: memory leak if calling request_irq too often
Date: Thu, 18 Jul 2002 16:35:48 +0200	[thread overview]
Message-ID: <20020718143548.29805@192.168.4.1> (raw)
In-Reply-To: <20020718162923.A7305@w-la.dhcp.softing.com>


>I found a memory leak, when called request_8xxirq again and again.
>This was already fixed for intel cpus, but the bug still exists in ppc
>code.
>
>You can easily see that the bug exists, if you see multiple directories
>in /proc/irq/ with the same name (drivers which already installed their
>irq-handler).

This have already been fixed in recent PPC kernels.

Thanks anyway,
Ben.


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

           reply	other threads:[~2002-07-18 14:35 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20020718162923.A7305@w-la.dhcp.softing.com>]

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=20020718143548.29805@192.168.4.1 \
    --to=benh@kernel.crashing.org \
    --cc=Gunnar.Larisch@softing.com \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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;
as well as URLs for NNTP newsgroup(s).