Eric Biggers cd9cb405e0 jbd2: don't leak memory if setting up journal fails ...

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.

Cc: stable@vger.kernel.org # 4.9
Fixes: f0c9fd5458bacf7b12a9a579a727dc740cbe047e
Signed-off-by: Eric Biggers <ebiggers@google.com>
Signed-off-by: Theodore Ts'o <tytso@mit.edu>
Reviewed-by: Jan Kara <jack@suse.cz>

2017-03-15 15:08:48 -04:00

..

checkpoint.c

block,fs: use REQ_* flags directly

2016-11-01 09:43:26 -06:00

commit.c

fs/jbd2, locking/mutex, sched/wait: Use mutex_lock_io() for journal->j_checkpoint_mutex

2017-01-14 11:30:06 +01:00

journal.c

jbd2: don't leak memory if setting up journal fails

2017-03-15 15:08:48 -04:00

Kconfig

…

Makefile

…

recovery.c

fs: have ll_rw_block users pass in op and flags separately

2016-06-07 13:41:38 -06:00

revoke.c

jbd2: don't leak memory if setting up journal fails

2017-03-15 15:08:48 -04:00

transaction.c

jbd2: don't leak modified metadata buffers on an aborted journal

2017-02-04 23:14:19 -05:00