From: Dave Chinner <david@fromorbit.com>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] XFS: Free buffer pages array unconditionally
Date: Wed, 16 Dec 2009 09:36:58 +1100 [thread overview]
Message-ID: <20091215223658.GD4850@discord.disaster> (raw)
In-Reply-To: <1AB9A794DBDDF54A8A81BE2296F7BDFE012A6866@cf--amer001e--3.americas.sgi.com>
On Tue, Dec 15, 2009 at 01:21:36PM -0600, Alex Elder wrote:
> Dave Chinner wrote:
> > The code in xfs_free_buf() only attempts to free the b_pages array if the
> > buffer is a page cache backed or page allocated buffer. The extra log buffer
> > that is used when the log wraps uses pages that are allocated to a different
> > log buffer, but it still has a b_pages array allocated when those pages
> > are associated to with the extra buffer in xfs_buf_associate_memory.
> >
> > Hence we need to always attempt to free the b_pages array when tearing
> > down a buffer, not just on buffers that are explicitly marked as page bearing
> > buffers. This fixes a leak detected by the kernel memory leak code.
>
> Three places call xfs_buf_get_pages();
> - _xfs_buf_lookup_pages(), which sets the _XBF_PAGE_CACHE flag in the
> buffer after the call
> - xfs_buf_associate_memory(), which sets no flag bit
> - xfs_buf_get_noaddr(), which sets the _XBF_PAGES flag.
>
> The only place that checks for _XBF_PAGES is xfs_buf_free().
>
> Given that, I have two comments:
> - You could just as easily have set the _XBF_PAGES flag in
> xfs_buf_associate_memory, thereby making that flag indicate
> consistently that the buffer has allocated pages
_XBF_PAGES is used to indicate that the buffer owns the
pages and must free them when the buffer is freed.
_XBF_PAGE_CACHE indicates pages are allocated out of the buftarg
page cache and need to be released when the buffer is freed.
In both cases, xfs_buf_free() has to free the pages
associated with these buffers.
In the case of xfs_buf_associate_memory(), the memory attached to
the buffer is owned by an external entity and hence we are not
allowed to free it when we free the buffer. Therefore we can't set
_XBF_PAGES on the buffer.
> - Or, since you are proposing unconditionally freeing the
> pages,
This change doesn't unconditionally free the pages attached
to the buffer - it unconditionally frees the array used to
index the pages on the buffer when the buffer is torn down.
i.e:
+------+ +------+
| bp | | |-------> page
| | b_pages | |-------> page
| |-------->| |.............
| | | |-------> page
| | | |-------> page
+------+ +------+
^^^^^^
This array is what we are
freeing unconditionally.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-12-15 22:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-14 23:11 [PATCH] XFS: Free buffer pages array unconditionally Dave Chinner
2009-12-15 19:21 ` Alex Elder
2009-12-15 22:36 ` Dave Chinner [this message]
2009-12-15 22:51 ` Alex Elder
-- strict thread matches above, loose matches on Subject: below --
2009-12-02 6:12 [PATCH] [XFS] " Dave Chinner
2009-12-02 15:17 ` Christoph Hellwig
2009-12-02 22:22 ` Dave Chinner
2009-12-04 10:15 ` Christoph Hellwig
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=20091215223658.GD4850@discord.disaster \
--to=david@fromorbit.com \
--cc=aelder@sgi.com \
--cc=xfs@oss.sgi.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