|| ||Andrew Morton <firstname.lastname@example.org>|
|| ||email@example.com, firstname.lastname@example.org|
|| ||Fri, 17 Jan 2003 00:24:51 -0800|
I've stripped these patches down to just those things which seriously should
go into Linus's tree.
I'm mainly interested in gathering bugfixes across the rest of this month,
but if people have more substantial things which are clearly 2.6 material and
need some testing then OK.
Changes since 2.5.58-mm1:
run-child-first didn't seem to help anything, and an alarming number of
cleanups and fixes were needed to get it working right. Later.
Not to Linus's taste.
This was just for trolling Manfred.
I/O scheduler changes from Nick.
Wasn't a serious patch anyway
Not sure we need this.
Fix the bug wherein ext3 sometimes shows blips of 100k context
Haven't tested this yet.
Nitin Kamble's rework of the ia32 SMP interrupt distribution logic.
Free truncated pages earlier from ext3 - should fix the strange "cannot
fork" thing which Con reports.
Not convinced about these.
Looks like nothing is happening here until Mr Viro returns.
This is 2.7 material.
Fix thinko in the ia32 stack overflow checker.
It's all right for him - he lives in Australia.
Header file safety.
All 34 patches:
remove lock_kernel() from exec of setuid apps
reiserfs v3 readpages support
ext3: fix scheduling storm and lockups
self-unplugging request queues
Remove most of the blk_run_queues() calls
hugetlb: fix MAP_FIXED handling
OSS ioctl bounds checking fix
ext3: explicitly free truncated pages
add stats for page reclaim via inode freeing
cleanup in read_cache_pages()
quota locking fix
quota semaphore fix
stack overflow checking fix
Subject: [PATCH] Richard Henderson for President!
Subject: i386 pgd_index() doesn't parenthesize its arg
Subject: Re: i386 pgd_index() doesn't parenthesize its arg
asm-i386/mmzone.h macro paren/eval fixes
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/