Tags give the ability to mark specific points in history as being important
-
-
xfs-merge-5.18_2022-04-07
919edbad · ·xfs: new code for 5.18 New code for 5.18, which so far is all bug fixes.
-
-
folio-5.18d
5a60542c · ·Filesystem/VFS changes for 5.18, part two - Remove ->readpages infrastructure - Remove AOP_FLAG_CONT_EXPAND - Move read_descriptor_t to networking code - Pass the iocb to generic_perform_write - Minor updates to iomap, btrfs, ext4, f2fs, ntfs
-
-
xfs-5.18-merge-4
919edbad · ·Bug fixes for 5.18: - Fix an incorrect free space calculation in xfs_reserve_blocks that could lead to a request for free blocks that will never succeed. - Fix a hang in xfs_reserve_blocks caused by an infinite loop and the incorrect free space calculation. - Fix yet a third problem in xfs_reserve_blocks where multiple racing threads can overfill the reserve pool. - Fix an accounting error that lead to us reporting reserved space as "available". - Fix a race condition during abnormal fs shutdown that could cause UAF problems when memory reclaim and log shutdown try to clean up inodes. - Fix a bug where log shutdown can race with unmount to tear down the log, thereby causing UAF errors. - Disentangle log and filesystem shutdown to reduce confusion. - Fix some confusion in xfs_trans_commit such that a race between transaction commit and filesystem shutdown can cause unlogged dirty inode metadata to be committed, thereby corrupting the filesystem. - Remove a performance optimization in the log as it was discovered that certain storage hardware handle async log flushes so poorly as to cause serious performance regressions. Recent restructuring of other parts of the logging code mean that no performance benefit is seen on hardware that handle it well.
-
vfs-5.18-merge-1
49df3422 · ·Fixes for 5.18-rc1: - Fix a potential infinite loop in FIEMAP by fixing an off by one error when comparing the requested range against s_maxbytes.