From: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
To: Curt Wohlgemuth <curtw@google.com>
Cc: ext4 development <linux-ext4@vger.kernel.org>
Subject: Re: [PATCH] ext4: More buffer head reference leaks
Date: Wed, 15 Jul 2009 11:22:27 +0530 [thread overview]
Message-ID: <20090715055227.GA17310@skywalker> (raw)
In-Reply-To: <6601abe90907141358w3b16cdb0rb429f8d67d65dc9a@mail.gmail.com>
On Tue, Jul 14, 2009 at 01:58:29PM -0700, Curt Wohlgemuth wrote:
> After the patch I posted last week regarding buffer head ref leaks in
> no-journal mode, I looked at all the code that uses buffer heads and
> searched for more potential leaks.
>
> The patch below fixes the issues I found; these can occur even when a
> journal is present.
>
> The change to inode.c fixes a double release if
> ext4_journal_get_create_access() fails.
>
> The changes to namei.c are more complicated. add_dirent_to_buf() will
> release the input buffer head EXCEPT when it returns -ENOSPC. There are
> some callers of this routine that don't always do the brelse() in the event
> that -ENOSPC is returned. Unfortunately, to put this fix into ext4_add_entry()
> required capturing the return value of make_indexed_dir() and
> add_dirent_to_buf().
>
> I'd appreciate comments on these changes, in particular if I'm just missing
> something obvious here.
>
> Signed-off-by: Curt Wohlgemuth <curtw@google.com>
>
> ---
> diff -Naur orig/fs/ext4/inode.c new/fs/ext4/inode.c
> --- orig/fs/ext4/inode.c 2009-07-14 11:19:01.000000000 -0700
> +++ new/fs/ext4/inode.c 2009-07-14 11:51:42.000000000 -0700
> @@ -758,8 +758,9 @@
> BUFFER_TRACE(bh, "call get_create_access");
> err = ext4_journal_get_create_access(handle, bh);
> if (err) {
> + /* Don't brelse(bh) here; it's done in journal_forget()
> + * below */
> unlock_buffer(bh);
> - brelse(bh);
> goto failed;
> }
>
I am not able to find the journal_foget call in the path. brelse is
dropping the buffer_head reference got from sb_getblk right ? Can you
tell me what is that i am missing ?
> diff -Naur orig/fs/ext4/namei.c new/fs/ext4/namei.c
> --- orig/fs/ext4/namei.c 2009-07-14 11:19:46.000000000 -0700
> +++ new/fs/ext4/namei.c 2009-07-14 11:19:28.000000000 -0700
> @@ -1498,12 +1498,14 @@
.. snip..
-aneesh
next prev parent reply other threads:[~2009-07-15 5:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 20:58 [PATCH] ext4: More buffer head reference leaks Curt Wohlgemuth
2009-07-15 5:52 ` Aneesh Kumar K.V [this message]
2009-07-15 15:00 ` Curt Wohlgemuth
2009-07-15 15:53 ` Curt Wohlgemuth
2009-07-17 19:55 ` Curt Wohlgemuth
2009-07-17 22:19 ` Theodore Tso
2009-07-15 6:23 ` Aneesh Kumar K.V
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=20090715055227.GA17310@skywalker \
--to=aneesh.kumar@linux.vnet.ibm.com \
--cc=curtw@google.com \
--cc=linux-ext4@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.