| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <45c1607a-805d-e7a2-a5ca-3fd7e507a664@huaweicloud.com>
Date: Thu, 29 Feb 2024 16:59:34 +0800
From: Zhang Yi <yi.zhang@...weicloud.com>
To: Dave Chinner <david@...morbit.com>
Cc: Christoph Hellwig <hch@...radead.org>, djwong@...nel.org,
linux-ext4@...r.kernel.org, linux-fsdevel@...r.kernel.org,
linux-mm@...ck.org, linux-kernel@...r.kernel.org, linux-xfs@...r.kernel.org,
tytso@....edu, adilger.kernel@...ger.ca, jack@...e.cz,
ritesh.list@...il.com, willy@...radead.org, zokeefe@...gle.com,
yi.zhang@...wei.com, chengzhihao1@...wei.com, yukuai3@...wei.com,
wangkefeng.wang@...wei.com
Subject: Re: [RFC PATCH v3 07/26] iomap: don't increase i_size if it's not a
write operation
Hello, Dave!
On 2024/2/29 6:25, Dave Chinner wrote:
> On Wed, Feb 28, 2024 at 04:53:32PM +0800, Zhang Yi wrote:
>> On 2024/2/13 13:46, Christoph Hellwig wrote:
>>> Wouldn't it make more sense to just move the size manipulation to the
>>> write-only code? An untested version of that is below. With this
>>> the naming of the status variable becomes even more confusing than
>>> it already is, maybe we need to do a cleanup of the *_write_end
>>> calling conventions as it always returns the passed in copied value
>>> or 0.
>>>
>>> diff --git a/fs/iomap/buffered-io.c b/fs/iomap/buffered-io.c
>>> index 3dab060aed6d7b..8401a9ca702fc0 100644
>>> --- a/fs/iomap/buffered-io.c
>>> +++ b/fs/iomap/buffered-io.c
>>> @@ -876,34 +876,13 @@ static size_t iomap_write_end(struct iomap_iter *iter, loff_t pos, size_t len,
>>> size_t copied, struct folio *folio)
>>> {
>>> const struct iomap *srcmap = iomap_iter_srcmap(iter);
>>> - loff_t old_size = iter->inode->i_size;
>>> - size_t ret;
>>> -
>>> - if (srcmap->type == IOMAP_INLINE) {
>>> - ret = iomap_write_end_inline(iter, folio, pos, copied);
>>> - } else if (srcmap->flags & IOMAP_F_BUFFER_HEAD) {
>>> - ret = block_write_end(NULL, iter->inode->i_mapping, pos, len,
>>> - copied, &folio->page, NULL);
>>> - } else {
>>> - ret = __iomap_write_end(iter->inode, pos, len, copied, folio);
>>> - }
>>> -
>>> - /*
>>> - * Update the in-memory inode size after copying the data into the page
>>> - * cache. It's up to the file system to write the updated size to disk,
>>> - * preferably after I/O completion so that no stale data is exposed.
>>> - */
>>> - if (pos + ret > old_size) {
>>> - i_size_write(iter->inode, pos + ret);
>>> - iter->iomap.flags |= IOMAP_F_SIZE_CHANGED;
>>> - }
>>
>> I've recently discovered that if we don't increase i_size in
>> iomap_zero_iter(), it would break fstests generic/476 on xfs. xfs
>> depends on iomap_zero_iter() to increase i_size in some cases.
>>
>> generic/476 75s ... _check_xfs_filesystem: filesystem on /dev/pmem2 is inconsistent (r)
>> (see /home/zhangyi/xfstests-dev/results//xfs/generic/476.full for details)
>>
>> _check_xfs_filesystem: filesystem on /dev/pmem2 is inconsistent (r)
>> *** xfs_repair -n output ***
>> Phase 1 - find and verify superblock...
>> Phase 2 - using internal log
>> - zero log...
>> - scan filesystem freespace and inode maps...
>> sb_fdblocks 10916, counted 10923
>> - found root inode chunk
>> ...
>>
>> After debugging and analysis, I found the root cause of the problem is
>> related to the pre-allocations of xfs. xfs pre-allocates some blocks to
>> reduce fragmentation during buffer append writing, then if we write new
>> data or do file copy(reflink) after the end of the pre-allocating range,
>> xfs would zero-out and write back the pre-allocate space(e.g.
>> xfs_file_write_checks() -> xfs_zero_range()), so we have to update
>> i_size before writing back in iomap_zero_iter(), otherwise, it will
>> result in stale delayed extent.
>
> Ok, so this is long because the example is lacking in clear details
> so to try to understand it I've laid it out in detail to make sure
> I've understood it correctly.
>
Thanks for the graph, the added detail makes things clear and easy to
understand. To be honest, it's not exactly the same as the results I
captured and described (the position A\B\C\D\E\F I described is
increased one by one), but the root cause of the problem is the same,
so it doesn't affect our understanding of the problem.
>>
>> For more details, let's think about this case,
>> 1. Buffered write from range [A, B) of an empty file foo, and
>> xfs_buffered_write_iomap_begin() prealloc blocks for it, then create
>> a delayed extent from [A, D).
>
> So we have a delayed allocation extent and the file size is now B
> like so:
>
> A B D
> +DDDDDDDDDDDDDDDDDDDDDD+dddddddddddddddddddd+
> EOF
> (in memory)
>
> where 'd' is a delalloc block with no data and 'D' is a delalloc
> block with dirty folios over it.
>
Yes
>> 2. Write back process map blocks but only convert above delayed extent
>> from [A, C) since the lack of a contiguous physical blocks, now we
>> have a left over delayed extent from [C, D), and the file size is B.
>
> So this produces:
>
> A C B D
> +wwwwwwwwww+DDDDDDDDDDD+dddddddddddddddddddd+
> EOF EOF
> (on disk) (in memory)
>
> where 'w' contains allocated written data blocks.
>
The results I captured is:
A B C D
+wwwwwwwwwwwwwwwwwwwwww+uuuuuuuuu+ddddddddddd+
EOF
(in memory)
(on disk)
>> 3. Copy range from another file to range [E, F), then
>> xfs_reflink_zero_posteof() would zero-out post eof range [B, E), it
>> writes zero, dirty and write back [C, E).
>
> I'm going to assume that [E,F) is located like this because you
> are talking about post-eof zeroing from B to E:
>
> A C B E F D
> +wwwwwwwwww+DDDDDDDDDDD+ddddd+rrrrrrr+dddddd+
> EOF EOF
> (on disk) (in memory)
>
> where 'r' is the clone destination over dellaloc blocks.
>
> Did I get that right?
>
The results I captured is:
A B C D E F
+wwwwwwwwwwwwwwwwwwwwww+uuuuuuuuu+dddddddddd+hhhhhh+rrrrrrr+
EOF
(in memory)
(on disk)
where 'h' contains a hole.
> And so reflink wants to zero [B,E] before it updates the file size,
> just like a truncate(E) would. iomap_zero_iter() will see a delalloc
> extent (IOMAP_DELALLOC) for [B,E], so it will write zeros into cache
> for it. We then have:
>
> A C B E F D
> +wwwwwwwwww+DDDDDDDDDDD+ZZZZZ+rrrrrrr+dddddd+
> EOF EOF
> (on disk) (in memory)
>
> where 'Z' is delalloc blocks with zeroes in cache.
>
The results I captured is:
A B C D E F
+wwwwwwwwwwwwwwwwwwwwww+uuuuuuuuu+ZZZZZZZZZZ+hhhhhh+rrrrrrr+
EOF
(in memory)
(on disk)
> Because the destination is post EOF, xfs_reflink_remap_prep() then
> does:
>
> /*
> * If pos_out > EOF, we may have dirtied blocks between EOF and
> * pos_out. In that case, we need to extend the flush and unmap to cover
> * from EOF to the end of the copy length.
> */
> if (pos_out > XFS_ISIZE(dest)) {
> loff_t flen = *len + (pos_out - XFS_ISIZE(dest));
> ret = xfs_flush_unmap_range(dest, XFS_ISIZE(dest), flen);
> } ....
>
> Which attempts to flush from the current in memory EOF up to the end
> of the clone destination range. This should result in:
>
> A C B E F D
> +wwwwwwwwww+DDDDDDDDDDD+zzzzz+rrrrrrr+dddddd+
> EOF EOF
> (on disk) (in memory)
>
> Where 'z' is zeroes on disk.
>
> Have I understood this correctly?
>
The results I captured is:
A B C D E F
+wwwwwwwwwwwwwwwwwwwwww+uuuuuuuuu+zzzzzzzzzz+hhhhhh+rrrrrrr+
EOF
(in memory)
(on disk)
Since we don't update i_size in iomap_zero_iter(), the zeroed C to D
in cache would never write back to disk (iomap_writepage_handle_eof()
would skip them since it's entirely ouside of i_size) and the
'i_size & i_disksize' is still at B, after reflink, the i_size would
be update to F, so the delayed C to D cannot be freed by
xfs_free_eofblocks().
A B C D E F
+wwwwwwwwwwwwwwwwwwwwww+uuuuuuuuu+dddddddddd+hhhhhh+rrrrrrr+
EOF
(in memory)
(on disk)
Although the result is not exactly the same as your understanding,
the situation you describe still triggers the problem.
> However, if this did actually write zeroes to disk, this would end
> up with:
>
> A C B E F D
> +wwwwwwwwww+DDDDDDDDDDD+zzzzz+rrrrrrr+dddddd+
> EOF EOF
> (in memory) (on disk)
>
> Which is wrong - the file extension and zeros should not get exposed
> to the user until the entire reflink completes. This would expose
> zeros at the EOF and a file size that the user never asked for after
> a crash. Experience tells me that they would report this as
> "filesystem corrupting data on crash".
>
> If we move where i_size gets updated by iomap_zero_iter(), we get:
>
> A C B E F D
> +wwwwwwwwww+DDDDDDDDDDD+zzzzz+rrrrrrr+dddddd+
> EOF
> (in memory)
> (on disk)
>
> Which is also wrong, because now the user can see the size change
> and read zeros in the middle of the clone operation, which is also
> wrong.
>
> IOWs, we do not want to move the in-memory or on-disk EOF as a
> result of zeroing delalloc extents beyond EOF as it opens up
> transient, non-atomic on-disk states in the event of a crash.
>
> So, catch-22: we need to move the in-memory EOF to write back zeroes
> beyond EOF, but that would move the on-disk EOF to E before the
> clone operation starts. i.e. it makes clone non-atomic.
Make sense. IIUC, I also notice that xfs_file_write_checks() zero
out EOF blocks if the later write offset is beyond the size of the
file. Think about if we replace the reflink operation to a buffer
write E to F, although it doesn't call xfs_flush_unmap_range()
directly, but if it could be raced by another background write
back, and trigger the same problem (I've not try to reproduce it,
so please correct me if I understand wrong).
>
> What should acutally result from the iomap_zero_range() call from
> xfs_reflink_remap_prep() is a state like this:
>
> A C B E F D
> +wwwwwwwwww+DDDDDDDDDDD+uuuuu+rrrrrrr+dddddd+
> EOF EOF
> (on disk) (in memory)
>
> where 'u' are unwritten extent blocks.
>
Yeah, this is a good solution.
In xfs_file_write_checks(), I don't fully understand why we need
the xfs_zero_range(). Theoretically, iomap have already handled
partial block zeroing for both buffered IO and DIO, so I guess
the only reason we still need it is to handle pre-allocated blocks
(no?). If so，would it be better to call xfs_free_eofblocks() to
release all the preallocated extents in range? If not, maybe we
could only zero out mapped partial blocks and also release
preallocated extents?
In xfs_reflink_remap_prep(), I read the commit 410fdc72b05a ("xfs:
zero posteof blocks when cloning above eof"), xfs used to release
preallocations, the change log said it didn't work because of the
PREALLOC flag, but the 'force' parameter is 'true' when calling
xfs_can_free_eofblocks(), so I don't get the problem met. Could we
fall back to use xfs_free_eofblocks() and make a state like this?
A C B E F D
+wwwwwwwwww+DDDDDDDDDDD+hhhhh+rrrrrrr+dddddd+
EOF EOF
(on disk) (in memory)
Thanks,
Yi.
> i.e. instead of writing zeroes through the page cache for
> IOMAP_DELALLOC ranges beyond EOF, we should be converting those
> ranges to unwritten and invalidating any cached data over that range
> beyond EOF.
>
> IOWs, it looks to me like the problem is that
> xfs_buffered_write_iomap_begin() is doing the wrong thing for
> IOMAP_ZERO operations for post-EOF regions spanned by speculative
> delalloc. It should be converting the region to unwritten so it has
> zeroes on disk, not relying on the page cache to be able to do
> writeback beyond the current EOF....
>
>> 4. Since we don't update i_size in iomap_zero_iter()，the writeback
>> doesn't write anything back, also doesn't convert the delayed extent.
>> After copy range, the file size will update to F.
>
> Yup, this is all, individually, correct behaviour. But when put
> together, the wrong thing happens. I suspect xfs_zero_range() needs
> to provide a custom set of iomap_begin/end callbacks rather than
> overloading the normal buffered write mechanisms.
>
> -Dave.
>
Powered by blists - more mailing lists