From: Fabian Frederick <fabf@skynet.be>
To: tytso@mit.edu, Andreas Dilger <adilger.kernel@dilger.ca>
Cc: linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, fabf@skynet.be
Subject: [PATCH 0/6 linux-next] ext4: fix extent leaking and clean-up
Date: Wed, 24 Aug 2016 22:03:14 +0200 [thread overview]
Message-ID: <1472069000-18897-1-git-send-email-fabf@skynet.be> (raw)
Last patch of this small patchset fixes an extent path memory leak.
The rest is some clean-up.
Fabian Frederick (6):
ext4: avoid EXT4_INODE_EXTENTS double checking
ext4: remove unneeded test in ext4_alloc_file_blocks()
ext4: create EXT4_MAX_BLOCKS() macro
ext4: use bool for check in ext4_ext_space_()
ext4: remove unused definition
ext4: fix memory leak in ext4_insert_range()
fs/ext4/ext4.h | 3 +++
fs/ext4/extents.c | 70 ++++++++++++++++++++-----------------------------------
fs/ext4/file.c | 3 +--
fs/ext4/ioctl.c | 2 --
4 files changed, 29 insertions(+), 49 deletions(-)
--
2.8.1
next reply other threads:[~2016-08-24 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-24 20:03 Fabian Frederick [this message]
2016-08-24 20:03 ` [PATCH 1/6 linux-next] ext4: avoid EXT4_INODE_EXTENTS double checking Fabian Frederick
2016-09-15 15:43 ` Theodore Ts'o
2016-08-24 20:03 ` [PATCH 2/6 linux-next] ext4: remove unneeded test in ext4_alloc_file_blocks() Fabian Frederick
2016-09-15 15:52 ` Theodore Ts'o
2016-08-24 20:03 ` [PATCH 3/6 linux-next] ext4: create EXT4_MAX_BLOCKS() macro Fabian Frederick
2016-09-15 15:55 ` Theodore Ts'o
2016-08-24 20:03 ` [PATCH 4/6 linux-next] ext4: use bool for check in ext4_ext_space_() Fabian Frederick
2016-09-15 15:57 ` Theodore Ts'o
2016-08-24 20:03 ` [PATCH 5/6 linux-next] ext4: remove unused definition Fabian Frederick
2016-09-15 15:59 ` Theodore Ts'o
2016-08-24 20:03 ` [PATCH 6/6 linux-next] ext4: fix memory leak in ext4_insert_range() Fabian Frederick
2016-09-15 15:40 ` Theodore Ts'o
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=1472069000-18897-1-git-send-email-fabf@skynet.be \
--to=fabf@skynet.be \
--cc=adilger.kernel@dilger.ca \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).