Re: [PATCH -next v6 2/2] iomap: don't increase i_size in iomap_write_end()
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: [PATCH -next v6 2/2] iomap: don't increase i_size in iomap_write_end()
From
: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date
: Tue, 18 Jun 2024 22:57:57 -0700
Cc
: linux-xfs@xxxxxxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, djwong@xxxxxxxxxx, hch@xxxxxxxxxxxxx, brauner@xxxxxxxxxx, david@xxxxxxxxxxxxx, chandanbabu@xxxxxxxxxx, jack@xxxxxxx, yi.zhang@xxxxxxxxxx, chengzhihao1@xxxxxxxxxx, yukuai3@xxxxxxxxxx
In-reply-to
: <
20240618142112.1315279-3-yi.zhang@huaweicloud.com
>
References
: <
20240618142112.1315279-1-yi.zhang@huaweicloud.com
> <
20240618142112.1315279-3-yi.zhang@huaweicloud.com
>
Looks good: Reviewed-by: Christoph Hellwig <hch@xxxxxx>
References
:
[PATCH -next v6 0/2] iomap/xfs: fix stale data exposure when truncating realtime inodes
From:
Zhang Yi
[PATCH -next v6 2/2] iomap: don't increase i_size in iomap_write_end()
From:
Zhang Yi
Prev by Date:
Re: [PATCH] xfs_repair: don't leak the rootdir inode when orphanage already exists
Next by Date:
Re: [PATCH 01/10] misc: split swapext and exchangerange
Previous by thread:
[PATCH -next v6 2/2] iomap: don't increase i_size in iomap_write_end()
Next by thread:
[PATCH -next v6 1/2] xfs: reserve blocks for truncating large realtime inode
Index(es):
Date
Thread
[Index of Archives]
[XFS Filesystem Development (older mail)]
[Linux Filesystem Development]
[Linux Audio Users]
[Yosemite Trails]
[Linux Kernel]
[Linux RAID]
[Linux SCSI]
