From: Larry Chen <lchen@suse.com>
To: mark@fasheh.com, jlbec@evilplan.org
Cc: linux-kernel@vger.kernel.org, ocfs2-devel@oss.oracle.com,
akpm@linux-foundation.org
Subject: [PATCH 0/2] fix cluster leakage in ocfs2_defrag_extent
Date: Tue, 4 Sep 2018 12:16:19 +0800 [thread overview]
Message-ID: <20180904041621.16874-1-lchen@suse.com> (raw)
ocfs2_defrag_extent might leak clusters allocated.
When file system has no enough space, the number of claimed clusters
might less than the caller wants. If that happens, the original code
might directly commit trans without returning clusters.
This patch refered a lot to ocfs2_add_clusters_in_btree.
Larry Chen (2):
add declaration of ocfs2_free_local_alloc_bits
fix clusters leak in ocfs2_defrag_extent
fs/ocfs2/alloc.h | 6 ++++++
fs/ocfs2/move_extents.c | 16 ++++++++++++++++
2 files changed, 22 insertions(+)
--
2.13.7
next reply other threads:[~2018-09-04 4:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 4:16 Larry Chen [this message]
2018-09-04 4:16 ` [PATCH 1/2] add declaration of ocfs2_free_local_alloc_bits Larry Chen
2018-09-04 21:55 ` Andrew Morton
2018-09-04 4:16 ` [PATCH 2/2] fix clusters leak in ocfs2_defrag_extent Larry Chen
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=20180904041621.16874-1-lchen@suse.com \
--to=lchen@suse.com \
--cc=akpm@linux-foundation.org \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark@fasheh.com \
--cc=ocfs2-devel@oss.oracle.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®