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

ext4: fix on-line resizing regression

2010-12-23T20:00:54Z

https://bugzilla.kernel.org/show_bug.cgi?id=25352 This regression was caused by commit a31437b85: "ext4: use sb_issue_zeroout in setup_new_group_blocks", by accidentally dropping the code which reserved the block group descriptor and inode table blocks. 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: rename mark_bitmap_end() to ext4_mark_bitmap_end()

2010-10-28T01:30:15Z

Fix a namespace leak from fs/ext4 Signed-off-by: "Theodore Ts'o"

ext4: use sb_issue_zeroout in setup_new_group_blocks

2010-10-28T01:30:05Z

Use sb_issue_zeroout to zero out inode table and descriptor table blocks instead of old approach which involves journaling. Signed-off-by: Lukas Czerner 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: Clean up s_dirt handling

2010-06-12T03:14:04Z

We don't need to set s_dirt in most of the ext4 code when journaling is enabled. In ext3/4 some of the summary statistics for # of free inodes, blocks, and directories are calculated from the per-block group statistics when the file system is mounted or unmounted. As a result the superblock doesn't have to be updated, either via the journal or by setting s_dirt. There are a few exceptions, most notably when resizing the file system, where the superblock needs to be modified --- and in that case it should be done as a journalled operation if possible, and s_dirt set only in no-journal mode. This patch will optimize out some unneeded disk writes when using ext4 with a journal. Signed-off-by: "Theodore Ts'o"

ext4: check s_log_groups_per_flex in online resize code

2010-05-16T05:00:00Z

If groups_per_flex < 2, sbi->s_flex_groups[] doesn't get filled out, and every other access to this first tests s_log_groups_per_flex; same thing needs to happen in resize or we'll wander off into a null pointer when doing an online resize of the file system. Thanks to Christoph Biedl, who came up with the trivial testcase: # truncate --size 128M fsfile # mkfs.ext3 -F fsfile # tune2fs -O extents,uninit_bg,dir_index,flex_bg,huge_file,dir_nlink,extra_isize fsfile # e2fsck -yDf -C0 fsfile # truncate --size 132M fsfile # losetup /dev/loop0 fsfile # mount /dev/loop0 mnt # resize2fs -p /dev/loop0 https://bugzilla.kernel.org/show_bug.cgi?id=13549 Reported-by: Alessandro Polverini Test-case-by: Christoph Biedl Signed-off-by: Eric Sandeen Signed-off-by: "Theodore Ts'o"

ext4: move func into a macro for ext4_warning, ext4_error

2010-02-15T19:19:27Z

Just a pet peeve of mine; we had a mishash of calls with either __func__ or "function_name" and the latter tends to get out of sync. I think it's easier to just hide the __func__ in a macro, and it'll be consistent from then on. Signed-off-by: Eric Sandeen Signed-off-by: "Theodore Ts'o"

ext4: Return the PTR_ERR of the correct pointer in setup_new_group_blocks()

2009-12-07T15:38:16Z

Signed-off-by: Roel Kluin Signed-off-by: "Theodore Ts'o"

ext4: Clarify the locking details in mballoc

2009-09-10T03:50:17Z

We don't need to take the alloc_sem lock when we are adding new groups, since mballoc won't see the new group added until we bump sbi->s_groups_count. Signed-off-by: "Theodore Ts'o" Signed-off-by: Aneesh Kumar K.V