From: Chris Wright <chrisw@osdl.org>
To: "Adam J. Richter" <adam@yggdrasil.com>
Cc: maneesh@in.ibm.com, akpm@osdl.org, chrisw@osdl.org,
greg@kroah.com, linux-kernel@vger.kernel.org,
viro@parcelfarce.linux.theplanet.co.uk
Subject: Re: [PATCH 2.6.10-rc2-bk15] sysfs_dir_close memory leak
Date: Thu, 2 Dec 2004 21:19:32 -0800 [thread overview]
Message-ID: <20041202211932.I2357@build.pdx.osdl.net> (raw)
In-Reply-To: <200412030250.iB32oZQ02969@adam.yggdrasil.com>; from adam@yggdrasil.com on Thu, Dec 02, 2004 at 06:50:35PM -0800
* Adam J. Richter (adam@yggdrasil.com) wrote:
> sysfs_dir_close did not free the "cursor" sysfs_dirent
> used for keeping track of position in the list of sysfs_dirent nodes.
> Consequently, doing a "find /sys" would leak a sysfs_dirent for
> each of the 1140 directories in my /sys tree, or about 36kB
> each time.
Yeah, I noticed this as well. Why the BUGON()?
thanks,
-chris
next prev parent reply other threads:[~2004-12-03 5:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-03 2:50 Adam J. Richter
2004-12-03 5:19 ` Chris Wright [this message]
2004-12-03 11:05 ` Adam J. Richter
2004-12-03 18:56 ` Greg KH
2004-12-04 2:39 Adam J. Richter
2004-12-04 7:35 ` Chris Wright
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=20041202211932.I2357@build.pdx.osdl.net \
--to=chrisw@osdl.org \
--cc=adam@yggdrasil.com \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maneesh@in.ibm.com \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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
Powered by JetHome