From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "David Chinner" <dgc@sgi.com>
Cc: xfs-masters@oss.sgi.com, xfs@oss.sgi.com,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Jesper Juhl" <jesper.juhl@gmail.com>
Subject: Re: [RFC][PATCH] XFS: memory leak in xfs_inactive() - is xfs_trans_free() enough or do we need xfs_trans_cancel() ?
Date: Thu, 24 May 2007 14:03:16 +0200 [thread overview]
Message-ID: <9a8748490705240503u25728daaj1b5ad010953b16a5@mail.gmail.com> (raw)
In-Reply-To: <200705180053.56070.jesper.juhl@gmail.com>
Any chance the patches below that fix two mem leaks in XFS will make
it in in time for 2.6.22? I believe they should...
On 18/05/07, Jesper Juhl <jesper.juhl@gmail.com> wrote:
> On Thursday 17 May 2007 04:40:24 David Chinner wrote:
> > On Wed, May 16, 2007 at 11:31:16PM +0200, Jesper Juhl wrote:
> > > Hi,
> > >
> > > The Coverity checker found a memory leak in xfs_inactive().
> > ....
> > > So, the code allocates a transaction, but in the case where 'truncate' is
> > > !=0 and xfs_itruncate_start(ip, XFS_ITRUNC_DEFINITE, 0); happens to return
> > > an error, we'll just return from the function without dealing with the
> > > memory allocated byxfs_trans_alloc() and assigned to 'tp', thus it'll be
> > > orphaned/leaked - not good.
> >
> > Yeah, introduced by:
> >
> > http://git2.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=d3cf209476b72c83907a412b6708c5e498410aa7
> >
> > Thanks for reporting the problem, Jesper.
> >
> You are welcome.
>
> That commit introduces the same problem in xfs_inactive_free_eofblocks().
> Patch to fix it below.
>
> > > What I'm wondering is this; is it enough, at this point, to call
> > > xfs_trans_free(tp); (it would seem to me that would be OK, but I'm not
> > > intimite with this code) or do we need a full xfs_trans_cancel(tp, 0); ???
> >
> > xfs_trans_free() is not supposed to be called by anything but the transaction
> > code (it's static). So a xfs_trans_cancel() would need to be issued.
> >
> Makes sense. Thanks. I completely missed the static nature :-/
>
>
>
> Fix XFS memory leak; allocated transaction not freed in xfs_inactive_free_eofblocks() in failure case.
>
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
> ---
> fs/xfs/xfs_vnodeops.c | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/fs/xfs/xfs_vnodeops.c b/fs/xfs/xfs_vnodeops.c
> index de17aed..32519cf 100644
> --- a/fs/xfs/xfs_vnodeops.c
> +++ b/fs/xfs/xfs_vnodeops.c
> @@ -1260,6 +1260,7 @@ xfs_inactive_free_eofblocks(
> error = xfs_itruncate_start(ip, XFS_ITRUNC_DEFINITE,
> ip->i_size);
> if (error) {
> + xfs_trans_cancel(tp, 0);
> xfs_iunlock(ip, XFS_IOLOCK_EXCL);
> return error;
> }
>
>
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2007-05-24 12:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 21:31 Jesper Juhl
2007-05-17 2:40 ` David Chinner
2007-05-17 22:53 ` Jesper Juhl
2007-05-24 12:03 ` Jesper Juhl [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=9a8748490705240503u25728daaj1b5ad010953b16a5@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=dgc@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xfs-masters@oss.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
all inboxes | Powered by JetHome®