From: Dmitry Monakhov <dmonakhov@openvz.org>
To: Theodore Ts'o <tytso@mit.edu>, Lukas 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 09:54:41 +0400 [thread overview]
Message-ID: <87k3o94noe.fsf@openvz.org> (raw)
In-Reply-To: <20130411035826.GA18878@thunk.org>
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
On Wed, 10 Apr 2013 23:58:26 -0400, Theodore Ts'o <tytso@mit.edu> wrote:
> On Tue, Apr 09, 2013 at 01:24:46PM +0200, Lukas Czerner wrote:
> > Move ext4_ind_migrate() into migrate.c file since it makes much more
> > sense and ext4_ext_migrate() is there as well.
> >
> > Also fix tiny style problem - add spaces around "=" in "i=0".
> >
> > Signed-off-by: Lukas Czerner <lczerner@redhat.com>
>
> I had to regenerate this patch since ext4_ind_migrate has been changed
> by other patches in the ext4 patch queue, but it's applied now.
You have placed it in to wrong position, Obviously check should be performed before
journal_start()
[-- Attachment #2: fix --]
[-- Type: application/octet-stream, Size: 694 bytes --]
diff --git a/fs/ext4/migrate.c b/fs/ext4/migrate.c
index 8d64067..8052070 100644
--- a/fs/ext4/migrate.c
+++ b/fs/ext4/migrate.c
@@ -625,13 +625,14 @@ 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);
- if (EXT4_HAS_RO_COMPAT_FEATURE(inode->i_sb,
- EXT4_FEATURE_RO_COMPAT_BIGALLOC))
- return -EOPNOTSUPP;
down_write(&EXT4_I(inode)->i_data_sem);
ret = ext4_ext_check_inode(inode);
[-- Attachment #3: Type: text/plain, Size: 234 bytes --]
>
> - Ted
> --
> 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 5:54 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 [this message]
2013-04-11 8:18 ` Lukáš Czerner
2013-04-11 14:56 ` Theodore Ts'o
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=87k3o94noe.fsf@openvz.org \
--to=dmonakhov@openvz.org \
--cc=gnehzuil.liu@gmail.com \
--cc=lczerner@redhat.com \
--cc=linux-ext4@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 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.