kernel.git/fs/jfs, branch linux-2.6.13.y

[PATCH] jfs: jfs_delete_inode must call clear_inode

2005-09-17T01:01:58Z

JFS: jfs_delete_inode should always call clear_inode. > From Chuck Ebbert: I'm submitting this patch for -stable: - it reportedly fixes an oops - it's already in 2.6.13-git Signed-off-by: Dave Kleikamp Signed-off-by: Chris Wright

[PATCH] Fix up symlink function pointers

2005-08-20T01:08:21Z

This fixes up the symlink functions for the calling convention change: * afs, autofs4, befs, devfs, freevxfs, jffs2, jfs, ncpfs, procfs, smbfs, sysvfs, ufs, xfs - prototype change for ->follow_link() * befs, smbfs, xfs - same for ->put_link() Signed-off-by: Linus Torvalds

JFS: Fix race in txLock

2005-08-10T16:14:39Z

TxAnchor.anon_list is protected by jfsTxnLock (TXN_LOCK), but there was a place in txLock() that was removing an entry from the list without holding the spinlock. Signed-off-by: Dave Kleikamp

JFS: Check for invalid inodes in jfs_delete_inode

2005-08-01T21:54:26Z

Some error paths may iput an invalid inode with i_nlink=0. jfs should not try to actually delete such an inode. Signed-off-by: Dave Kleikamp

JFS: Improve sync barrier processing

2005-07-27T14:17:57Z

Under heavy load, hot metadata pages are often locked by non-committed transactions, making them difficult to flush to disk. This prevents the sync point from advancing past a transaction that had modified the page. There is a point during the sync barrier processing where all outstanding transactions have been committed to disk, but no new transaction have been allowed to proceed. This is the best time to write the metadata. Signed-off-by: Dave Kleikamp

JFS: Fix i_blocks accounting when allocation fails

2005-07-26T14:29:13Z

A failure in dbAlloc caused a directory's i_blocks to be incorrectly incremented, causing jfs_fsck to find the inode to be corrupt. Signed-off-by: Dave Kleikamp

JFS: Don't set log_SYNCBARRIER when log->active == 0

2005-07-25T13:58:54Z

If a metadata page is kept active, it is possible that the sync barrier logic continues to trigger, even if all active transactions have been phyically written to the journal. This can cause a hang, since the completion of the journal I/O is what unsets the sync barrier flag to allow new transactions to be created. Signed-off-by: Dave Kleikamp

JFS: Fix typo in last patch

2005-07-22T16:08:44Z

Signed-off-by: Dave Kleikamp

JFS: fsync wrong behavior when I/O failure occurs

2005-07-15T15:36:08Z

This is half of a patch that Qu Fuping submitted in April. The first part was applied to fs/mpage.c in 2.6.12-rc4. jfs_fsync should return error, but it doesn't wait for the metadata page to be uptodate, e.g.: jfs_fsync->jfs_commit_inode->txCommit->diWrite->read_metapage-> __get_metapage->read_cache_page reads a page from disk. Because read is async, when read_cache_page: err = filler(data, page), filler will not return error, it just submits I/O request and returns. So, page is not uptodate. Checking only if(IS_ERROR(mp->page)) is not enough, we should add "|| !PageUptodate(mp->page)" Signed-off-by: Dave Kleikamp

JFS: Remove assert statement in dbJoin & return -EIO instead

2005-07-15T14:43:36Z

Signed-off-by: Dave Kleikamp