summaryrefslogtreecommitdiffstats
path: root/fs/jfs/jfs_metapage.c
Commit message (Collapse)AuthorAgeFilesLines
* JFS: Fix typo in last patchDave Kleikamp2005-07-221-1/+1
| | | | Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
* JFS: fsync wrong behavior when I/O failure occursQu Fuping2005-07-151-1/+1
| | | | | | | | | | | | | | | | 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 <shaggy@austin.ibm.com>
* JFS: Remove bogus WARN_ON statement and some dead codeDave Kleikamp2005-07-141-9/+0
| | | | Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
* JFS: Fix sparse warningDave Kleikamp2005-05-041-1/+1
| | | | Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
* JFS: fix sparse warnings by moving extern declarations to headersDave Kleikamp2005-05-041-2/+2
| | | | Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
* [PATCH] JFS: Support page sizes greater than 4KDave Kleikamp2005-05-021-307/+601
| | | | | | | jfs has never worked on architecutures where the page size was not 4K. Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
* Linux-2.6.12-rc2v2.6.12-rc2Linus Torvalds2005-04-161-0/+580
Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!
OpenPOWER on IntegriCloud