From: Jaegeuk Kim <jaegeuk@kernel.org>
To: linux-f2fs-devel@lists.sourceforge.net
Cc: Jaegeuk Kim <jaegeuk@kernel.org>
Subject: [PATCH 1/7] defrag.f2fs: return error for no space case
Date: Wed, 2 Nov 2016 22:28:40 -0700 [thread overview]
Message-ID: <20161103052846.72244-1-jaegeuk@kernel.org> (raw)
This returns error instead of assertion for resize.f2fs.
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
---
fsck/defrag.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/fsck/defrag.c b/fsck/defrag.c
index 079e7a7..bea0293 100644
--- a/fsck/defrag.c
+++ b/fsck/defrag.c
@@ -78,8 +78,8 @@ int f2fs_defragment(struct f2fs_sb_info *sbi, u64 from, u64 len, u64 to, int lef
continue;
if (find_next_free_block(sbi, &target, left, se->type)) {
- ASSERT_MSG("Not enough space to migrate blocks");
- break;
+ MSG(0, "Not enough space to migrate blocks");
+ return -1;
}
if (migrate_block(sbi, idx, target)) {
--
2.8.3
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
next reply other threads:[~2016-11-03 5:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-03 5:28 Jaegeuk Kim [this message]
2016-11-03 5:28 ` [PATCH 2/7] resize.f2fs: fix wrong end_blkaddr Jaegeuk Kim
2016-11-03 5:28 ` [PATCH 3/7] f2fs-tools: fix end block addres when finding free block Jaegeuk Kim
2016-11-03 5:28 ` [PATCH 4/7] resize.f2fs: get latest free segments Jaegeuk Kim
2016-11-03 6:53 ` heyunlei
2016-11-03 17:26 ` Jaegeuk Kim
2016-11-03 17:36 ` Jaegeuk Kim
2016-11-03 5:28 ` [PATCH 5/7] sload.f2fs: not support to find or add files in inline_dir directory Jaegeuk Kim
2016-11-03 5:28 ` [PATCH 6/7] f2fs-tools: determine cp_addr by sbi->cur_cp Jaegeuk Kim
2016-11-03 5:28 ` [PATCH 7/7] resize.f2fs: fill zeros for expanded ssa area Jaegeuk Kim
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=20161103052846.72244-1-jaegeuk@kernel.org \
--to=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
/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.