From: Sebastian Witt <hasw@hasw.net>
To: GW <gw.kernel@tnode.com>
Cc: cpufreq@lists.linux.org.uk
Subject: Re: Memory leak in cpufreq-nforce2.c
Date: Fri, 24 Aug 2007 19:43:38 +0200 [thread overview]
Message-ID: <46CF18CA.1020209@hasw.net> (raw)
In-Reply-To: <46CD7BE6.5040904@tnode.com>
Hello,
GW wrote:
>
> This means that there are some memory leaks in the following driver that uses pci_get_subsys(), but no pci_dev_put():
>
Yes, pci_dev_put(nforce2_chipset_dev) is missing in nforce2_exit()...
> I don't have this chip, therefore I couldn't test a patch if I would written it.
...unfortunately I don't own the original hardware with nForce2 chipset anymore.
I don't think a patch for correcting this bug modifies the expected
behaviour...but it should be tested by someone who ones compatible hardware.
Regards,
Sebastian
prev parent reply other threads:[~2007-08-24 17:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 12:21 Memory leak in cpufreq-nforce2.c GW
2007-08-24 17:43 ` Sebastian Witt [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=46CF18CA.1020209@hasw.net \
--to=hasw@hasw.net \
--cc=cpufreq@lists.linux.org.uk \
--cc=gw.kernel@tnode.com \
/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