public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] [XFS] Free buffer pages array unconditionally
Date: Thu, 3 Dec 2009 09:22:28 +1100	[thread overview]
Message-ID: <20091202222228.GN30608@discord.disaster> (raw)
In-Reply-To: <20091202151742.GA1263@infradead.org>

On Wed, Dec 02, 2009 at 10:17:42AM -0500, Christoph Hellwig wrote:
> On Wed, Dec 02, 2009 at 05:12:13PM +1100, 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.
> > 
> > Signed-off-by: Dave Chinner <david@fromorbit.com>
> > ---
> >  fs/xfs/linux-2.6/xfs_buf.c |    4 ++--
> >  1 files changed, 2 insertions(+), 2 deletions(-)
> > 
> > diff --git a/fs/xfs/linux-2.6/xfs_buf.c b/fs/xfs/linux-2.6/xfs_buf.c
> > index 4ddc973..4b84bbc 100644
> > --- a/fs/xfs/linux-2.6/xfs_buf.c
> > +++ b/fs/xfs/linux-2.6/xfs_buf.c
> > @@ -316,7 +316,7 @@ STATIC void
> >  _xfs_buf_free_pages(
> >  	xfs_buf_t	*bp)
> >  {
> > -	if (bp->b_pages != bp->b_page_array) {
> > +	if (bp->b_pages && bp->b_pages != bp->b_page_array) {
> >  		kmem_free(bp->b_pages);
> 
> kmem_free happily takes a NULL pointer, so this is unessecary.

Yes, it does, but I wanted to make sure that b_pages had been
assigned before doing the comparison because this is now
called unconditionally. I´ll remove the check and retest.

Hmmm - I suspect that this function needs to NULL b_pages
in case it _xfs_buf_free_pages() is called prior to calling
xfs_buf_free()...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-12-02 22:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02  6:12 [PATCH] [XFS] Free buffer pages array unconditionally Dave Chinner
2009-12-02 15:17 ` Christoph Hellwig
2009-12-02 22:22   ` Dave Chinner [this message]
2009-12-04 10:15     ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2009-12-14 23:11 [PATCH] XFS: " Dave Chinner
2009-12-15 19:21 ` Alex Elder
2009-12-15 22:36   ` Dave Chinner
2009-12-15 22:51     ` Alex Elder

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=20091202222228.GN30608@discord.disaster \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --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