From: Jan Kara <jack@suse.cz>
To: Theodore Ts'o <tytso@mit.edu>
Cc: Ashlie Martinez <ashmrtn@utexas.edu>,
Amir Goldstein <amir73il@gmail.com>,
Xiao Yang <yangx.jy@cn.fujitsu.com>, Eryu Guan <eguan@redhat.com>,
Josef Bacik <jbacik@fb.com>, fstests <fstests@vger.kernel.org>,
Ext4 <linux-ext4@vger.kernel.org>,
Vijay Chidambaram <vvijay03@gmail.com>
Subject: Re: [PATCH] ext4: fix interaction between i_size, fallocate, and delalloc after a crash
Date: Thu, 12 Oct 2017 16:38:59 +0200 [thread overview]
Message-ID: <20171012143859.GA31488@quack2.suse.cz> (raw)
In-Reply-To: <20171007032917.bntgnubthdstmrrt@thunk.org>
> commit 3912e7b44cf77e9452d4d0cb6c1da9c7043bb7f1
> Author: Theodore Ts'o <tytso@mit.edu>
> Date: Fri Oct 6 23:09:55 2017 -0400
>
> ext4: fix interaction between i_size, fallocate, and delalloc after a crash
>
> If there are pending writes subject to delayed allocation, then i_size
> will show size after the writes have completed, while i_disksize
> contains the value of i_size on the disk (since the writes have not
> been persisted to disk).
>
> If fallocate(2) is called with the FALLOC_FL_KEEP_SIZE flag, either
> with or without the FALLOC_FL_ZERO_RANGE flag set, and the new size
> after the fallocate(2) is between i_size and i_disksize, then after a
> crash, if a journal commit has resulted in the changes made by the
> fallocate() call to be persisted after a crash, but the delayed
> allocation write has not resolved itself, i_size would not be updated,
> and this would cause the following e2fsck complaint:
>
> Inode 12, end of extent exceeds allowed value
> (logical block 33, physical block 33441, len 7)
>
> This can only take place on a sparse file, where the fallocate(2) call
> is allocating blocks in a range which is before a pending delayed
> allocation write which is extending i_size. Since this situation is
> quite rare, and the window in which the crash must take place is
> typically < 30 seconds, in practice this condition will rarely happen.
>
> Nevertheless, it can be triggered in testing, and in particular by
> xfstests generic/456.
>
> Signed-off-by: Theodore Ts'o <tytso@mit.edu>
> Reported-by: Amir Goldstein <amir73il@gmail.com>
> Cc: stable@vger.kernel.org
The patch looks good to me. You can add:
Reviewed-by: Jan Kara <jack@suse.cz>
Honza
>
> diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
> index 97f0fd06728d..07bca11749d4 100644
> --- a/fs/ext4/extents.c
> +++ b/fs/ext4/extents.c
> @@ -4794,7 +4794,8 @@ static long ext4_zero_range(struct file *file, loff_t offset,
> }
>
> if (!(mode & FALLOC_FL_KEEP_SIZE) &&
> - offset + len > i_size_read(inode)) {
> + (offset + len > i_size_read(inode) ||
> + offset + len > EXT4_I(inode)->i_disksize)) {
> new_size = offset + len;
> ret = inode_newsize_ok(inode, new_size);
> if (ret)
> @@ -4965,7 +4966,8 @@ long ext4_fallocate(struct file *file, int mode, loff_t offset, loff_t len)
> }
>
> if (!(mode & FALLOC_FL_KEEP_SIZE) &&
> - offset + len > i_size_read(inode)) {
> + (offset + len > i_size_read(inode) ||
> + offset + len > EXT4_I(inode)->i_disksize)) {
> new_size = offset + len;
> ret = inode_newsize_ok(inode, new_size);
> if (ret)
--
Jan Kara <jack@suse.com>
SUSE Labs, CR
prev parent reply other threads:[~2017-10-12 14:39 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 10:44 [RFC][PATCH] fstest: regression test for ext4 crash consistency bug Amir Goldstein
2017-09-25 9:49 ` Xiao Yang
2017-09-25 10:53 ` Amir Goldstein
2017-09-26 10:45 ` Xiao Yang
2017-09-26 11:48 ` Amir Goldstein
2017-09-30 14:15 ` Ashlie Martinez
2017-10-05 7:27 ` Xiao Yang
2017-10-05 15:04 ` Ashlie Martinez
2017-10-05 19:10 ` Amir Goldstein
2017-10-06 0:34 ` Ashlie Martinez
2017-10-07 3:29 ` [PATCH] ext4: fix interaction between i_size, fallocate, and delalloc after a crash Theodore Ts'o
2017-10-07 5:54 ` Amir Goldstein
2017-10-07 18:32 ` Theodore Ts'o
2017-10-09 0:37 ` Ashlie Martinez
2017-10-11 11:11 ` Xiao Yang
2017-10-11 13:17 ` Ashlie Martinez
2017-10-11 13:34 ` Amir Goldstein
2017-10-16 19:32 ` Ashlie Martinez
2017-10-16 21:11 ` Amir Goldstein
2017-10-17 0:09 ` Theodore Ts'o
2017-10-17 1:02 ` Vijay Chidambaram
[not found] ` <CAPaz=E+jFuOmRk8+EmVhNawwogNzW3VkciFrCc0Fk23OfGbwuA@mail.gmail.com>
2017-10-17 7:15 ` Amir Goldstein
2017-10-17 14:41 ` Theodore Ts'o
2017-10-17 23:16 ` Vijay Chidambaram
2017-10-12 14:38 ` Jan Kara [this message]
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=20171012143859.GA31488@quack2.suse.cz \
--to=jack@suse.cz \
--cc=amir73il@gmail.com \
--cc=ashmrtn@utexas.edu \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=jbacik@fb.com \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=vvijay03@gmail.com \
--cc=yangx.jy@cn.fujitsu.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;
as well as URLs for NNTP newsgroup(s).