An error occurred fetching the project authors.
- 18 Aug, 2004 1 commit
-
-
Dave Kleikamp authored
This patch adds disk quota support to jfs. A patch is required for quota-tools to work with jfs. It can be found at http://oss.software.ibm.com/jfs/project/pub/quota-tools.patch Quota tools source can be downloaded from https://sourceforge.net/projects/linuxquota/ Written by: Karl Rister & Dave Kleikamp Signed-off-by: Dave Kleikamp <shaggy@austin.ibm.com>
-
- 08 Oct, 2003 1 commit
-
-
Dave Kleikamp authored
This patch replaces many assert statements, which caused a BUG(), with improved code to mark the superblock dirty and then proceed as specified by the errors= mount flag (as ext2 and ext3 do). JFS's default for the errors option is "remount-ro" in order to prevent addition data corruption when a problem is found. These asserts are usually triggered by on-disk data corruption. By marking the superblock dirty, fsck will perform a complete check on the file system and correct the problems, rather than simply replaying the journal, inviting later trouble. Submitted by Karl Rister & Dave Kleikamp
-
- 03 Jul, 2003 1 commit
-
-
Dave Kleikamp authored
JFS was often returning positive error return codes. This was confusing and awkward. Patch originally submitted by Thomas Cort.
-
- 29 May, 2003 1 commit
-
-
Dave Kleikamp authored
Bmap control page was not always being updated. Superblock's s_size field was incorrectly set on big-endian hardware.
-
- 10 Feb, 2003 1 commit
-
-
Andrew Morton authored
Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz> points out a bug in ll_rw_block() usage. Typical usage is: mark_buffer_dirty(bh); ll_rw_block(WRITE, 1, &bh); wait_on_buffer(bh); the problem is that if the buffer was locked on entry to this code sequence (due to in-progress I/O), ll_rw_block() will not wait, and start new I/O. So this code will wait on the _old_ I/O, and will then continue execution, leaving the buffer dirty. It turns out that all callers were only writing one buffer, and they were all waiting on that writeout. So I added a new sync_dirty_buffer() function: void sync_dirty_buffer(struct buffer_head *bh) { lock_buffer(bh); if (test_clear_buffer_dirty(bh)) { get_bh(bh); bh->b_end_io = end_buffer_io_sync; submit_bh(WRITE, bh); } else { unlock_buffer(bh); } } which allowed a fair amount of code to be removed, while adding the desired data-integrity guarantees. UFS has its own wrappers around ll_rw_block() which got in the way, so this operation was open-coded in that case.
-
- 20 Dec, 2002 1 commit
-
-
Dave Kleikamp authored
-
- 12 Sep, 2002 1 commit
-
-
Dave Kleikamp authored
-
- 02 Sep, 2002 1 commit
-
-
Christoph Hellwig authored
-
- 12 Aug, 2002 2 commits
-
-
David S. Miller authored
-
Dave Kleikamp authored
Kernel threads take a void * argument Fix compiler warnings in printk statement on 64-bit architectures
-
- 05 Aug, 2002 1 commit
-
-
Dave Kleikamp authored
This is invoked by mount -remount,resize=<blocks>. See Documentation/filesystems/jfs.txt for more information.
-