kernel.git/fs/ext4/namei.c, branch linux-2.6.37.y

ext4: fix typo which broke '..' detection in ext4_find_entry()

2010-12-15T02:45:31Z

There should be a check for the NUL character instead of '0'. Fortunately the only thing that cares about this is NFS serving, which is why we didn't notice this in the merge window testing. Reported-by: Phil Carmody Signed-off-by: Aaro Koskinen Signed-off-by: "Theodore Ts'o"

Merge branch 'next' into upstream-merge

2010-10-28T03:44:47Z

Conflicts: fs/ext4/inode.c fs/ext4/mballoc.c include/trace/events/ext4.h

ext4: use search_dirblock() in ext4_dx_find_entry()

2010-10-28T01:30:08Z

Use the search_dirblock() in ext4_dx_find_entry(). It makes the code easier to read, and it takes advantage of common code. It also saves 100 bytes or so of text space. Signed-off-by: "Theodore Ts'o" Cc: Brad Spengler

ext4: avoid uninitialized memory references in ext3_htree_next_block()

2010-10-28T01:30:08Z

If the first block of htree directory is missing '.' or '..' but is otherwise a valid directory, and we do a lookup for '.' or '..', it's possible to dereference an uninitialized memory pointer in ext4_htree_next_block(). We avoid this by moving the special case from ext4_dx_find_entry() to ext4_find_entry(); this also means we can optimize ext4_find_entry() slightly when NFS looks up "..". Thanks to Brad Spengler for pointing a Clang warning that led me to look more closely at this code. The warning was harmless, but it was useful in pointing out code that was too ugly to live. This warning was also reported by Roman Borisov. Signed-off-by: "Theodore Ts'o" Cc: Brad Spengler

new helper: ihold()

2010-10-26T01:26:11Z

Clones an existing reference to inode; caller must already hold one. Signed-off-by: Al Viro

ext4: re-inline ext4_rec_len_(to|from)_disk functions

2010-08-05T05:46:37Z

commit 3d0518f4, "ext4: New rec_len encoding for very large blocksizes" made several changes to this path, but from a perf perspective, un-inlining ext4_rec_len_from_disk() seems most significant. This function is called from ext4_check_dir_entry(), which on a file-creation workload is called extremely often. I tested this with bonnie: # bonnie++ -u root -s 0 -f -x 200 -d /mnt/test -n 32 (this does 200 iterations) and got this for the file creations: ext4 stock: Average = 21206.8 files/s ext4 inlined: Average = 22346.7 files/s (+5%) Signed-off-by: Eric Sandeen Signed-off-by: "Theodore Ts'o"

ext4: Cleanup ext4_check_dir_entry so func is now implicit

2010-07-27T15:54:40Z

Also start passing the line number to ext4_check_dir since we're going to need it in upcoming patch. Signed-off-by: "Theodore Ts'o"

ext4: remove initialized but not read variables

2010-06-14T17:28:03Z

No real bugs found, just removed some dead code. Found by gcc 4.6's new warnings. Signed-off-by: Andi Kleen Signed-off-by: "Theodore Ts'o"

ext4: Make fsync sync new parent directories in no-journal mode

2010-05-17T12:00:00Z

Add a new ext4 state to tell us when a file has been newly created; use that state in ext4_sync_file in no-journal mode to tell us when we need to sync the parent directory as well as the inode and data itself. This fixes a problem in which a panic or power failure may lose the entire file even when using fsync, since the parent directory entry is lost. Addresses-Google-Bug: #2480057 Signed-off-by: Frank Mayhar Signed-off-by: "Theodore Ts'o"

ext4: Drop whitespace at end of lines

2010-05-17T11:00:00Z

This patch was generated using: #!/usr/bin/perl -i while (<>) { s/[ ]+$//; print; } Signed-off-by: "Theodore Ts'o"