From: Theodore Ts'o <tytso@mit.edu>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: linux-ext4@vger.kernel.org, gnehzuil.liu@gmail.com
Subject: Re: [PATCH 1/2 v2] ext4: move ext4_ind_migrate() into migrate.c
Date: Thu, 11 Apr 2013 10:56:20 -0400 [thread overview]
Message-ID: <20130411145620.GC8609@thunk.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1304111013191.10609@dhcp-1-230.brq.redhat.com>
On Thu, Apr 11, 2013 at 10:18:16AM +0200, Lukáš Czerner wrote:
> Thanks, but Dmitry is right, the check should be before the
> journal_start() call.
Whoops! I'm not sure how I screwed that up. Thanks for catching
that, Dmitry!
> I am not sure how much work will it be for you, but would it be
> possible to resend patch to the list when you change it ? Just to
> make sure we do not get unnecessary problems.
Yes, I'll try to do that in the future. Here's the revised patch....
- Ted
commit 3b296c66fe6f9a6ed44b0b83f4f2ae87d8874af6
Author: Lukas Czerner <lczerner@redhat.com>
Date: Thu Apr 11 10:54:46 2013 -0400
ext4: do not convert to indirect with bigalloc enabled
With bigalloc feature enabled we do not support indirect addressing at all
so we have to prevent extent addressing to indirect addressing
conversion in this case. The problem has been introduced with the commit
"ext4: support simple conversion of extent-mapped inodes to use i_blocks"
Signed-off-by: Lukas Czerner <lczerner@redhat.com>
Signed-off-by: "Theodore Ts'o" <tytso@mit.edu>
diff --git a/fs/ext4/migrate.c b/fs/ext4/migrate.c
index d129a4d..49e8bdf 100644
--- a/fs/ext4/migrate.c
+++ b/fs/ext4/migrate.c
@@ -625,6 +625,10 @@ int ext4_ind_migrate(struct inode *inode)
(!ext4_test_inode_flag(inode, EXT4_INODE_EXTENTS)))
return -EINVAL;
+ if (EXT4_HAS_RO_COMPAT_FEATURE(inode->i_sb,
+ EXT4_FEATURE_RO_COMPAT_BIGALLOC))
+ return -EOPNOTSUPP;
+
handle = ext4_journal_start(inode, EXT4_HT_MIGRATE, 1);
if (IS_ERR(handle))
return PTR_ERR(handle);
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-04-11 14:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 11:24 [PATCH 1/2 v2] ext4: move ext4_ind_migrate() into migrate.c Lukas Czerner
2013-04-09 11:24 ` [PATCH 2/2 v2] ext4: Do not convert to indirect with bigalloc enabled Lukas Czerner
2013-04-09 12:48 ` Zheng Liu
2013-04-11 3:58 ` Theodore Ts'o
2013-04-09 12:47 ` [PATCH 1/2 v2] ext4: move ext4_ind_migrate() into migrate.c Zheng Liu
2013-04-11 3:58 ` Theodore Ts'o
2013-04-11 5:54 ` Dmitry Monakhov
2013-04-11 8:18 ` Lukáš Czerner
2013-04-11 14:56 ` Theodore Ts'o [this message]
2013-04-11 15:15 ` Lukáš Czerner
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=20130411145620.GC8609@thunk.org \
--to=tytso@mit.edu \
--cc=gnehzuil.liu@gmail.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@vger.kernel.org \
/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).