From: Jan Kara <jack@suse.cz>
To: Daeho Jeong <daeho.jeong@samsung.com>
Cc: tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/3] ext4: enable again per-file data journaling on delalloc mode
Date: Mon, 30 Nov 2015 15:09:59 +0100 [thread overview]
Message-ID: <20151130140959.GF4522@quack.suse.cz> (raw)
In-Reply-To: <1447810474-14840-3-git-send-email-daeho.jeong@samsung.com>
On Wed 18-11-15 10:34:34, Daeho Jeong wrote:
> Several problems occurred when per-file data journaling is enabled on
> "delalloc" mode, so the per-file data journaling was permanently
> deactivated by commit 3d2b15826282 ("ext4: ignore
> EXT4_INODE_JOURNAL_DATA flag with delalloc"). But, those are not
> problems for only "delalloc" mode and when you execute xfstest on
> "nodelalloc" mode, same problems happen on "nodelalloc" mode. We always
> execute xfstest on "delalloc" mode, which is default mode, so we
> haven't realized problems of per-file data journaling feature. Finally,
> problems of per-file data journaling feature were fixed by commit
> 9c02ac97989d ("ext4: fix xfstest generic/269 double revoked buffer bug
> with bigalloc") and previous patchset. Now, we can re-enable the
> feature on "delalloc" mode.
Yeah, once we fix what I pointed out for patch 2/3 and we fix races with
page faults, this should be OK to do.
Honza
> Signed-off-by: Daeho Jeong <daeho.jeong@samsung.com>
> ---
> fs/ext4/ext4_jbd2.h | 4 +---
> 1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/fs/ext4/ext4_jbd2.h b/fs/ext4/ext4_jbd2.h
> index 9c5b49f..742b3ec 100644
> --- a/fs/ext4/ext4_jbd2.h
> +++ b/fs/ext4/ext4_jbd2.h
> @@ -395,12 +395,10 @@ static inline int ext4_inode_journal_mode(struct inode *inode)
> {
> if (EXT4_JOURNAL(inode) == NULL)
> return EXT4_INODE_WRITEBACK_DATA_MODE; /* writeback */
> - /* We do not support data journalling with delayed allocation */
> if (!S_ISREG(inode->i_mode) ||
> test_opt(inode->i_sb, DATA_FLAGS) == EXT4_MOUNT_JOURNAL_DATA)
> return EXT4_INODE_JOURNAL_DATA_MODE; /* journal data */
> - if (ext4_test_inode_flag(inode, EXT4_INODE_JOURNAL_DATA) &&
> - !test_opt(inode->i_sb, DELALLOC))
> + if (ext4_test_inode_flag(inode, EXT4_INODE_JOURNAL_DATA))
> return EXT4_INODE_JOURNAL_DATA_MODE; /* journal data */
> if (test_opt(inode->i_sb, DATA_FLAGS) == EXT4_MOUNT_ORDERED_DATA)
> return EXT4_INODE_ORDERED_DATA_MODE; /* ordered */
> --
> 1.7.9.5
>
> --
> 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
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
next prev parent reply other threads:[~2015-11-30 14:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-18 1:34 [PATCH 1/3] ext4: handle unwritten or delalloc buffers before enabling per-file data journaling Daeho Jeong
2015-11-18 1:34 ` [PATCH 2/3] ext4: remove incorrect check for inode journal mode in ext4_writepages() Daeho Jeong
2015-11-30 14:08 ` Jan Kara
2015-11-18 1:34 ` [PATCH 3/3] ext4: enable again per-file data journaling on delalloc mode Daeho Jeong
2015-11-30 14:09 ` Jan Kara [this message]
2015-11-30 13:45 ` [PATCH 1/3] ext4: handle unwritten or delalloc buffers before enabling per-file data journaling Jan Kara
2015-11-30 13:55 ` Jan Kara
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=20151130140959.GF4522@quack.suse.cz \
--to=jack@suse.cz \
--cc=daeho.jeong@samsung.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 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).