litmus2008.git, branch v2.6.15-rc3

Linux v2.6.15-rc3

2005-11-29T03:51:27+00:00

Merge master.kernel.org:/home/rmk/linux-2.6-serial

2005-11-28T23:03:28+00:00

Merge master.kernel.org:/home/rmk/linux-2.6-mmc

2005-11-28T23:02:50+00:00

Merge master.kernel.org:/home/rmk/linux-2.6-arm

2005-11-28T23:02:30+00:00

[PATCH] fuse: check for invalid node ID in fuse_create_open()

2005-11-28T22:42:26+00:00

Check for invalid node ID values in the new atomic create+open method.

Signed-off-by: Miklos Szeredi 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] fuse: check directory aliasing in mkdir

2005-11-28T22:42:26+00:00

Check the created directory inode for aliases in the mkdir() method.

Signed-off-by: Miklos Szeredi 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] shrinker->nr = LONG_MAX means deadlock for icache

2005-11-28T22:42:26+00:00

With Andrew Morton 

The slab scanning code tries to balance the scanning rate of slabs versus the
scanning rate of LRU pages.  To do this, it retains state concerning how many
slabs have been scanned - if a particular slab shrinker didn't scan enough
objects, we remember that for next time, and scan more objects on the next
pass.

The problem with this is that with (say) a huge number of GFP_NOIO
direct-reclaim attempts, the number of objects which are to be scanned when we
finally get a GFP_KERNEL request can be huge.  Because some shrinker handlers
just bail out if !__GFP_FS.

So the patch clamps the number of objects-to-be-scanned to 2* the total number
of objects in the slab cache.

Signed-off-by: Andrea Arcangeli 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] Fix oops in vfs_quotaon_mount()

2005-11-28T22:42:26+00:00

When quota file specified in mount options did not exist, we tried to
dereference NULL pointer later. Fix it.

Signed-off-by: Jan Kara 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] md: fix --re-add for raid1 and raid6

2005-11-28T22:42:26+00:00

If you have an array with a write-intent-bitmap, and you remove a device, then
re-add it, a full recovery isn't needed.  We detect a re-add by looking at
saved_raid_disk.  For raid1, it doesn't matter which disk it was, only whether
or not it was an active device.  The old code being removed set a value of
'mirror' which was then ignored, so it can go.  The changed code performs the
correct check.

For raid6, if there are two missing devices, make sure we chose the right slot
on --re-add rather than always the first slot.

Signed-off-by: Neil Brown 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] md: set default_bitmap_offset properly in set_array_info

2005-11-28T22:42:25+00:00

If an array is created using set_array_info, default_bitmap_offset isn't set
properly meaning that an internal bitmap cannot be hot-added until the array
is stopped and re-assembled.

Signed-off-by: Neil Brown 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds