public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Eric Biggers <ebiggers3@gmail.com>
Cc: linux-ext4@vger.kernel.org, Theodore Ts'o <tytso@mit.edu>,
	Jan Kara <jack@suse.com>, Eric Biggers <ebiggers@google.com>
Subject: Re: [PATCH] jbd2: don't leak memory if setting up journal fails
Date: Wed, 15 Mar 2017 12:39:50 +0100	[thread overview]
Message-ID: <20170315113950.GE12989@quack2.suse.cz> (raw)
In-Reply-To: <20170315041955.30687-1-ebiggers3@gmail.com>

On Tue 14-03-17 21:19:55, Eric Biggers wrote:
> From: Eric Biggers <ebiggers@google.com>
> 
> In journal_init_common(), if we failed to allocate the j_wbuf array, or
> if we failed to create the buffer_head for the journal superblock, we
> leaked the memory allocated for the revocation tables.  Fix this.
> 
> Signed-off-by: Eric Biggers <ebiggers@google.com>

Looks good. You can add:

Reviewed-by: Jan Kara <jack@suse.cz>

								Honza

> ---
>  fs/jbd2/journal.c | 22 +++++++++++-----------
>  fs/jbd2/revoke.c  |  1 +
>  2 files changed, 12 insertions(+), 11 deletions(-)
> 
> diff --git a/fs/jbd2/journal.c b/fs/jbd2/journal.c
> index a1a359bfcc9c..5adc2fb62b0f 100644
> --- a/fs/jbd2/journal.c
> +++ b/fs/jbd2/journal.c
> @@ -1125,10 +1125,8 @@ static journal_t *journal_init_common(struct block_device *bdev,
>  
>  	/* Set up a default-sized revoke table for the new mount. */
>  	err = jbd2_journal_init_revoke(journal, JOURNAL_REVOKE_DEFAULT_HASH);
> -	if (err) {
> -		kfree(journal);
> -		return NULL;
> -	}
> +	if (err)
> +		goto err_cleanup;
>  
>  	spin_lock_init(&journal->j_history_lock);
>  
> @@ -1145,23 +1143,25 @@ static journal_t *journal_init_common(struct block_device *bdev,
>  	journal->j_wbufsize = n;
>  	journal->j_wbuf = kmalloc_array(n, sizeof(struct buffer_head *),
>  					GFP_KERNEL);
> -	if (!journal->j_wbuf) {
> -		kfree(journal);
> -		return NULL;
> -	}
> +	if (!journal->j_wbuf)
> +		goto err_cleanup;
>  
>  	bh = getblk_unmovable(journal->j_dev, start, journal->j_blocksize);
>  	if (!bh) {
>  		pr_err("%s: Cannot get buffer for journal superblock\n",
>  			__func__);
> -		kfree(journal->j_wbuf);
> -		kfree(journal);
> -		return NULL;
> +		goto err_cleanup;
>  	}
>  	journal->j_sb_buffer = bh;
>  	journal->j_superblock = (journal_superblock_t *)bh->b_data;
>  
>  	return journal;
> +
> +err_cleanup:
> +	kfree(journal->j_wbuf);
> +	jbd2_journal_destroy_revoke(journal);
> +	kfree(journal);
> +	return NULL;
>  }
>  
>  /* jbd2_journal_init_dev and jbd2_journal_init_inode:
> diff --git a/fs/jbd2/revoke.c b/fs/jbd2/revoke.c
> index cfc38b552118..f9aefcda5854 100644
> --- a/fs/jbd2/revoke.c
> +++ b/fs/jbd2/revoke.c
> @@ -280,6 +280,7 @@ int jbd2_journal_init_revoke(journal_t *journal, int hash_size)
>  
>  fail1:
>  	jbd2_journal_destroy_revoke_table(journal->j_revoke_table[0]);
> +	journal->j_revoke_table[0] = NULL;
>  fail0:
>  	return -ENOMEM;
>  }
> -- 
> 2.12.0
> 
> 
-- 
Jan Kara <jack@suse.com>
SUSE Labs, CR

      reply	other threads:[~2017-03-15 11:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-15  4:19 [PATCH] jbd2: don't leak memory if setting up journal fails Eric Biggers
2017-03-15 11:39 ` Jan Kara [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=20170315113950.GE12989@quack2.suse.cz \
    --to=jack@suse.cz \
    --cc=ebiggers3@gmail.com \
    --cc=ebiggers@google.com \
    --cc=jack@suse.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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