- 16 Sep, 2020 40 commits
-
-
Darrick J. Wong authored
The V4 filesystem format contains known weaknesses in the on-disk format that make metadata verification diffiult. In addition, the format does not support dates past 2038 and will not be upgraded to do so. We should start the process of retiring the old format to close off attack surfaces and to encourage users to migrate onto V5. Therefore, make XFS V4 support a configurable option. For the first period it will be default Y in case some distributors want to withdraw support early; for the second period it will be default N so that anyone who wishes to continue support can do so; and after that, support will be removed from the kernel. Dates for these events have been added to the upstream kernel. Signed-off-by:
Darrick J. Wong <darrick.wong@oracle.com> Reviewed-by:
Dave Chinner <dchinner@redhat.com> Reviewed-by:
Eric Sandeen <sandeen@redhat.com>
-
Darrick J. Wong authored
While running generic/042 with -drtinherit=1 set in MKFS_OPTIONS, I observed that the kernel will gladly set the realtime flag on any file created on the loopback filesystem even though that filesystem doesn't actually have a realtime device attached. This leads to verifier failures and doesn't make any sense, so be smarter about this. Signed-off-by:
Christoph Hellwig <hch@lst.de>
-
Darrick J. Wong authored
Hoist the code that propagates di_flags and di_flags2 from a parent to a new child into separate functions. No functional changes. Signed-off-by:
-
Darrick J. Wong authored
Make sure that any fallocate operation that requires the range to be block-aligned also checks that the range is aligned to the realtime extent size. Signed-off-by:
-
Darrick J. Wong authored
There's an overflow bug in the realtime allocator. If the rt volume is large enough to handle a single allocation request that is larger than the maximum bmap extent length and the rt bitmap ends exactly on a bitmap block boundary, it's possible that the near allocator will try to check the freeness of a range that extends past the end of the bitmap. This fails with a corruption error and shuts down the fs. Therefore, constrain maxlen so that the range scan cannot run off the end of the rt bitmap. Signed-off-by:
-
Zheng Bin authored
Fixes coccicheck warning: fs/xfs/xfs_icache.c:1214:2-3: Unneeded semicolon Signed-off-by:
Zheng Bin <zhengbin13@huawei.com> Reviewed-by:
-
Darrick J. Wong authored
Commit 5833112d tried to make it so that a remap operation would force the log out to disk if the filesystem is mounted with mandatory synchronous writes. Unfortunately, that commit failed to handle the case where the inode or the file descriptor require mandatory synchronous writes. Refactor the check into into a helper that will look for all three conditions, and now we can treat reflink just like any other synchronous write. Fixes: 5833112d ("xfs: reflink should force the log out if mounted with wsync") Signed-off-by:
Brian Foster <bfoster@redhat.com> Reviewed-by:
-
Carlos Maiolino authored
xfs_attr_sf_totsize() requires access to xfs_inode structure, so, once xfs_attr_shortform_addname() is its only user, move it to xfs_attr.c instead of playing with more #includes. Reviewed-by:
Carlos Maiolino <cmaiolino@redhat.com> Signed-off-by:
-
Carlos Maiolino authored
nameval is a variable-size array, so, define it as it, and remove all the -1 magic number subtractions Reviewed-by:
-
Carlos Maiolino authored
Reviewed-by:
-
Carlos Maiolino authored
Reviewed-by:
-
Carlos Maiolino authored
This patch aims to replace kmem_zalloc_large() with global kernel memory API. So, all its callers are now using kvzalloc() directly, so kmalloc() fallsback to vmalloc() automatically. Signed-off-by:
-
Darrick J. Wong authored
Enable the big timestamp feature. Signed-off-by:
Amir Goldstein <amir73il@gmail.com> Reviewed-by:
Allison Collins <allison.henderson@oracle.com> Reviewed-by:
Gao Xiang <hsiangkao@redhat.com> Reviewed-by:
-
Darrick J. Wong authored
Add a couple of tracepoints so that we can check the timestamp limits being set on inodes and quotas. Signed-off-by:
-
Darrick J. Wong authored
Enable the bigtime feature for quota timers. We decrease the accuracy of the timers to ~4s in exchange for being able to set timers up to the bigtime maximum. Signed-off-by:
-
Darrick J. Wong authored
Redesign the ondisk inode timestamps to be a simple unsigned 64-bit counter of nanoseconds since 14 Dec 1901 (i.e. the minimum time in the 32-bit unix time epoch). This enables us to handle dates up to 2486, which solves the y2038 problem. Signed-off-by:
-
Darrick J. Wong authored
Redefine xfs_ictimestamp_t as a uint64_t typedef in preparation for the bigtime functionality. Preserve the legacy structure format so that we can let the compiler take care of the masking and shifting. Signed-off-by:
-
Darrick J. Wong authored
Redefine xfs_timestamp_t as a __be64 typedef in preparation for the bigtime functionality. Preserve the legacy structure format so that we can let the compiler take care of masking and shifting. Signed-off-by:
-
Darrick J. Wong authored
Move this function to xfs_inode_item_recover.c since there's only one caller of it. Signed-off-by:
-
Darrick J. Wong authored
Refactor quota timestamp encoding and decoding into helper functions so that we can add extra behavior in the next patch. Signed-off-by:
-
Darrick J. Wong authored
Refactor the code that sets the default quota grace period into a helper function so that we can override the ondisk behavior later. Signed-off-by:
-
Darrick J. Wong authored
Define explicit limits on the range of quota grace period expiration timeouts and refactor the code that modifies the timeouts into helpers that clamp the values appropriately. Note that we'll refactor the default grace period timer separately. Signed-off-by:
-
Darrick J. Wong authored
Formally define the inode timestamp ranges that existing filesystems support, and switch the vfs timetamp ranges to use it. Signed-off-by:
-
Darrick J. Wong authored
Enable the new inode btree counters feature. Signed-off-by:
-
Darrick J. Wong authored
Add the necessary bits to the online repair code to support logging the inode btree counters when rebuilding the btrees, and to support fixing the counters when rebuilding the AGI. Signed-off-by:
-
Darrick J. Wong authored
Add the necessary bits to the online scrub code to check the inode btree counters when enabled. Signed-off-by:
-
Darrick J. Wong authored
Now that we have reliable finobt block counts, use them to speed up the per-AG block reservation calculations at mount time. Signed-off-by:
-
Darrick J. Wong authored
Add a btree block usage counters for both inode btrees to the AGI header so that we don't have to walk the entire finobt at mount time to create the per-AG reservations. Signed-off-by:
-
Christoph Hellwig authored
Instead of poking deeply into buffer cache internals when re-reading the superblock during log recovery just generalize _xfs_buf_read and use it there. Note that we don't have to explicitly set up the ops as they must be set from the initial read. Signed-off-by:
-
Christoph Hellwig authored
Merge xfs_getsb into its only caller, and clean that one up a little bit as well. Signed-off-by:
-
Christoph Hellwig authored
Remove the mp argument as this function is only called in transaction context, and open code xfs_getsb given that the function already accesses the buffer pointer in the mount point directly. Signed-off-by:
-
Christoph Hellwig authored
The log recovery I/O completion handler does not substancially differ from the normal one except for the fact that it: a) never retries failed writes b) can have log items that aren't on the AIL c) never has inode/dquot log items attached and thus don't need to handle them Add conditionals for (a) and (b) to the ioend code, while (c) doesn't need special handling anyway. Signed-off-by: -
Christoph Hellwig authored
Clear the flags at the end of xfs_buf_ioend so that they can be used during the completion. Signed-off-by:
-
Christoph Hellwig authored
Reuse xfs_buf_item_relse instead of duplicating it. Signed-off-by:
-
Christoph Hellwig authored
Now that all the actual error handling is in a single place, xfs_buf_ioend_disposition just needs to return true if took ownership of the buffer, or false if not instead of the tristate. Also move the error check back in the caller to optimize for the fast path, and give the function a better fitting name. Signed-off-by:
-
Christoph Hellwig authored
Keep all the error handling code together. Signed-off-by:
-
Christoph Hellwig authored
Merge xfs_buf_ioerror_retry into its only caller to make the resubmission flow a little easier to follow. Signed-off-by:
-
Christoph Hellwig authored
xfs_buf_ioerror_fail_without_retry is a somewhat weird function in that it has two trivial checks that decide the return value, while the rest implements a ratelimited warning. Just lift the two checks into the caller, and give the remainder a suitable name. Signed-off-by:
-
Christoph Hellwig authored
No need to keep a separate helper for this logic. Signed-off-by:
-
Christoph Hellwig authored
Move the buffer retry state machine logic to xfs_buf.c and call it once from xfs_ioend instead of duplicating it three times for the three kinds of buffers. Signed-off-by:
-
