src-test2/sys/ufs, branch release/5.5.0

MFC ffs_alloc.c 1.135 - clear i_flag field in recycled inodes

2005-10-08T20:04:28Z

The IN_HASHED bit should not be cleared here in RELENG_5. Original commit message: truckman 2005-10-03 21:57:43 UTC FreeBSD src repository Modified files: sys/ufs/ffs ffs_alloc.c Log: Initialize the inode i_flag field in ffs_valloc() to clean up any stale flag bits left over from before the inode was recycled. Without this change, a leftover IN_SPACECOUNTED flag could prevent softdep_freefile() and softdep_releasefile() from incrementing fs_pendinginodes. Because handle_workitem_freefile() unconditionally decrements fs_pendinginodes, a negative value could be reported at file system unmount time with a message like: unmount pending error: blocks 0 files -3 The pending block count in fs_pendingblocks could also be negative for similar reasons. These errors can cause the data returned by statfs() to be slightly incorrect. Some other cleanup code in softdep_releasefile() could also be incorrectly bypassed. MFC after: 3 days Revision Changes Path 1.135 +1 -0 src/sys/ufs/ffs/ffs_alloc.c

MFC ffs_softdep.c 1.185 - Schedule update of parent directory's link count

2005-10-08T05:57:40Z

after rmdir() Original commit message: truckman 2005-09-29 21:50:26 UTC FreeBSD src repository Modified files: sys/ufs/ffs ffs_softdep.c Log: After a rmdir()ed directory has been truncated, force an update of the directory's inode after queuing the dirrem that will decrement the parent directory's link count. This will force the update of the parent directory's actual link to actually be scheduled. Without this change the parent directory's actual link count would not be updated until ufs_inactive() cleared the inode of the newly removed directory, which might be deferred indefinitely. ufs_inactive() will not be called as long as any process holds a reference to the removed directory, and ufs_inactive() will not clear the inode if the link count is non-zero, which could be the result of an earlier system crash. If a background fsck is run before the update of the parent directory's actual link count has been performed, or at least scheduled by putting the dirrem on the leaf directory's inodedep id_bufwait list, fsck will corrupt the file system by decrementing the parent directory's effective link count, which was previously correct because it already took the removal of the leaf directory into account, and setting the actual link count to the same value as the effective link count after the dangling, removed, leaf directory has been removed. This happens because fsck acts based on the actual link count, which will be too high when fsck creates the file system snapshot that it references. This change has the fortunate side effect of more quickly cleaning up the large number dirrem structures that linger for an extended time after the removal of a large directory tree. It also fixes a potential problem with the shutdown of the syncer thread timing out if the system is rebooted immediately after removing a large directory tree. Submitted by: tegge MFC after: 3 days Revision Changes Path 1.185 +2 -0 src/sys/ufs/ffs/ffs_softdep.c Submitted by: tegge

MFC 1.64: Restore a historical ufs_inactive behavior that respect

2005-09-27T17:05:46Z

the RDONLY option, so subsequent call of UFS_TRUNCATE (ffs_truncate) would not panic the system. This fixes a panic that can happen when mounting a corrputed filesystem read-only, and reading data from it. Reviewed by: mckusick

MFC: Retain generation count when writing zeroes instead of an inode to disk.

2005-09-20T22:36:32Z

Don't free a struct inodedep if another process is allocating saved inode memory for the same struct inodedep in initiate_write_inodeblock_ufs[12](). Handle disappearing dependencies in softdep_disk_io_initiation().

Merge vfs_subr.c:1.646 (in spirit) from HEAD to RELENG_5:

2005-09-16T09:11:50Z

In vfs_kqfilter(), return EINVAL instead of 1 (EPERM) when an unsupported kqueue filter type is requested on a vnode.

Merge ufs_vnops.c:1.269 from HEAD to RELENG_5:

2005-09-07T16:23:06Z

Allow removal of empty directories with high link counts. These can occur on a filesystem running with soft updates after a crash and before a background fsck has been run. To prevent discrepancies from arising in a background fsck that may already be running, the directory is removed but its inode is not freed and is left with the residual reference count. When encountered by the background fsck it will be reclaimed. This change was present at the time of the RELENG_6 branch point, so does not need to be merged to RELENG_6. Approved by: mckusick Bumped into by: Mikhail Teterin

MFC: Don't set the COMPLETE flag in an inodedep structure before the

2005-08-26T20:40:31Z

related inode has been written.

MFC ffs_softdep.c 1.182, softdep.h 1.18

2005-08-10T15:22:17Z

Delay freeing disk space for file system blocks until all dirty buffers are safely released. This fixes softdep problems on truncation (deletion) of files with dirty buffers.

MFC: ufs_vnops.c 1.268

2005-04-23T12:29:22Z

- Plug memory leak. - Fix two style nits. Found by: Coverity Prevent analysis tool Reviewed by: rwatson

MFC revision 1.103.

2005-04-04T23:53:36Z

Security: FreeBSD-SA-05:02.sendfile