Here is a reworked implementation that restricts the code to the ipv6 module as Andi suggested. Uses the same CONFIG and sysctl variables as the ipv4 implementation. Signed-off-by: Glenn Griffin <ggriffin.kernel@gmail.com> --- include/net/tcp.h | 6 + net/ipv6/Makefile | 1 + net/ipv6/syncookies.c | 273 +++++++++++++++++++++++++++++++++++++++++++++++++ net/ipv6/tcp_ipv6.c | 77 ++++++++++---- 4 files changed, 335 insertions(+), 22 deletions(-) create mode 100644 net/...

Michael, can you provide which BIOS version had this issue and which version fixed the issue? ----------------------------------------------------------------------------------- This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. --...

Add anotations, so that timertop produces nicer results. Relative expiry time can get negative, so it should be signed. Signed-off-by: Pavel Machek <Pavel@suse.cz> diff --git a/arch/x86/kernel/hpet.c b/arch/x86/kernel/hpet.c index 429d084..235fd6c 100644 --- a/arch/x86/kernel/hpet.c +++ b/arch/x86/kernel/hpet.c @@ -368,8 +368,8 @@ static int hpet_clocksource_register(voi return 0; } -/* - * Try to setup the HPET timer +/** + * hpet_enable - Try to setup the HPET timer. Retur...

if (!buffer) is actually prefered style, so lets use it in example. Pavel Signed-off-by: Pavel Machek <pavel@suse.cz> diff --git a/Documentation/CodingStyle b/Documentation/CodingStyle index 6caa146..9bb2d8a 100644 --- a/Documentation/CodingStyle +++ b/Documentation/CodingStyle @@ -406,7 +415,7 @@ int fun(int a) int result = 0; char *buffer = kmalloc(SIZE); - if (buffer == NULL) + if (!buffer) return -ENOMEM; if (condition1) { -- (english) [ message continues ]

This is just an FYI. As part of the "Isolated CPU extensions" thread Daniel suggest for me to check out latest RT kernels. So I did or at least tried to and immediately spotted a couple of issues. The machine I'm running it on is: HP xw9300, Dual Opteron, NUMA It looks like with -rt kernel IRQ affinity masks are ignored on that system. ie I write 1 to lets say /proc/irq/23/smp_affinity but the interrupts keep coming to CPU1. Vanilla 2.6.24 does not have that issue. Also the first thing I tr...

It should be like this I guess? this patch was not yet tested, please confirm. -- Note the duplicate test 'SCpnt->sc_data_direction == DMA_FROM_DEVICE' from Documentation/DMA-API.txt: DMA_TO_DEVICE = PCI_DMA_TODEVICE data is going from the memory to the device DMA_FROM_DEVICE = PCI_DMA_FROMDEVICE data is coming from the device to the Signed-off-by: Roel Kluin <12o3l@tiscali.nl...

in drivers/scsi/NCR53C9x.c:412-422 it reads: else if(family_code == 0x00) { if ((version & 7) == 2) esp->erev = fas100a; /* NCR53C9X */ else esp->erev = espunknown; } else if(family_code == 0x14) { if ((version & 7) == 2) esp->erev = fsc; else ...

> /* safety net should the EC not support AUTO > * or FULLSPEED mode bits and just ignore them */ > if (level & TP_EC_FAN_FULLSPEED) > level |= 7; /* safety min speed 7 */ > else if (level & TP_EC_FAN_FULLSPEED) > level |= 4; /* safety min speed 4 */ > > Note the duplicate test 'if (level & TP_EC_FAN_FULLSPEED)'. should > this be re...

--=-Gf+l7GLQkygQGNdWrZqr Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi all, there is some serious problem with pata_cs5536 in linux 2.6.24 - it does not boot on ALIX.1B and ALIX.2C2 with hdd attached (as slave) to ide port. the ALIX.* are a series of single board computers, manufactured by PC Engines in switzerland. Systems are based on AMD Geode LX, which itself utilizes a CS5536 for IDE. ALIX.1B/1C use Award BIOS, while ALIX.2C2 and other use tinyBIOS. See http:...

Refuse to accept or create RT tasks in groups that can't run them. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> --- kernel/sched.c | 15 +++++++++++++++ 1 file changed, 15 insertions(+) Index: linux-2.6/kernel/sched.c =================================================================== --- linux-2.6.orig/kernel/sched.c +++ linux-2.6/kernel/sched.c @@ -4588,6 +4588,15 @@ recheck: return -EPERM; } +#ifdef CONFIG_RT_GROUP_SCHED + /* + * Do not allow realtime tasks ...

Clean up some of the excessive ifdeffery introduces in the last patch. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> --- kernel/sched.c | 150 ++++++++++++++++++++++++++++++++++++++------------------- 1 file changed, 100 insertions(+), 50 deletions(-) Index: linux-2.6/kernel/sched.c =================================================================== --- linux-2.6.orig/kernel/sched.c +++ linux-2.6/kernel/sched.c @@ -7563,56 +7563,29 @@ static int load_balance_monitor(void *un ...

Change the rt_ratio interface to rt_runtime_us, to match rt_period_us. This avoids picking a granularity for the ratio. Extend the /sys/kernel/uids/<uid>/ interface to allow setting the group's rt_runtime. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> --- Documentation/ABI/testing/sysfs-kernel-uids | 6 + Documentation/sched-rt-group.txt | 59 +++++++++++ include/linux/sched.h | 7 - kernel/sched.c | 14...

Currently the rt group scheduling does a per cpu runtime limit, however the rt load balancer makes no guarantees about an equal spread of real- time tasks, just that at any one time, the highest priority tasks run. Solve this by making the runtime limit a global property by borrowing excessive runtime from the other cpus once the local limit runs out. Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> --- kernel/sched.c | 38 ++++++++++++++++++++++- kernel/sched_rt.c | 88 +++++...

--

These are small cleanups all over the tree. Please apply, Signed-off-by: Pavel Machek <pavel@suse.cz> diff --git a/fs/select.c b/fs/select.c index 47f4792..c414aed 100644 --- a/fs/select.c +++ b/fs/select.c @@ -260,7 +260,7 @@ int do_select(int n, fd_set_bits *fds, s wait = NULL; if (retval || !*timeout || signal_pending(current)) break; - if(table.error) { + if (table.error) { retval = table.error; break; } diff --git a/kernel/signal.c b/kernel/signal.c inde...

Linus, please pull from: git://lost.foo-projects.org/~dwillia2/git/iop async-tx-for-linus to receive: Dan Williams (5): async_tx: fix compile breakage, mark do_async_xor __always_inline async_tx: kill ASYNC_TX_ASSUME_COHERENT async_tx: kill tx_set_src and tx_set_dest methods async_tx: replace 'int_en' with operation preparation flags async_tx: allow architecture specific async_tx_find_channel implementations Denis Cheng (2): async_tx: use LIST_HEAD inst...

All of the low mmap addr stuff isn't added until 2.6.23. thanks, -chris --

sorry, drop this .. /usr/data/source/oliver/build/linux-2.6.22.y-rcX-stable/mm/mmap.c: In function 'do_brk': /usr/data/source/oliver/build/linux-2.6.22.y-rcX-stable/mm/mmap.c:1889: error: too many arguments to function 'security_file_mmap' make[6]: *** [mm/mmap.o] Error 1 make[5]: *** [mm] Error 2 -- Thanks, Oliver --

http://nvd.nist.gov/nvd.cfm?cvename=CVE-2007-6434 -- Thanks, Oliver --

On Mon, 4 Feb 2008 12:08:34 -0800 (PST) err, what? I though I was going to merge these: slub-move-count_partial.patch slub-rename-numa-defrag_ratio-to-remote_node_defrag_ratio.patch slub-consolidate-add_partial-and-add_partial_tail-to-one-function.patch slub-use-non-atomic-bit-unlock.patch slub-fix-coding-style-violations.patch slub-noinline-some-functions-to-avoid-them-being-folded-into-alloc-free.patch slub-move-kmem_cache_node-determination-into-add_full-and-add_partial.patch slub-avoid-che...

While you're there, can you drop the patch(es?) I commented on and didn't get an answer to. Like the ones that open code their own locking primitives and do risky looking things with barriers to boot... Also, WRT this one: slub-use-non-atomic-bit-unlock.patch This is strange that it is unwanted. Avoiding atomic operations is a pretty good idea. The fact that it appears to be slower on some microbenchmark on some architecture IMO either means that their __clear_bit_unlock or the CPU isn't impl...

Hope to have the slub-mm repository setup tonight which will simplify things for the future. Hope you still remember .... --

Yes, my crash happens at kernel space, but is due to the randomized params passed to set_brk (the same thing that makes your game crash later at runtime). I did not understand why my kernel was crashing before reading your comments, but now I think is all happening because of the brk randomization. Sorry, I will not be able to try disabling randomization until tomorrow at office in order to confirm you this. I am trying to figure out what is relation the brk randomization feature and my crash....

You are rigth, my kernel just randomizes stack top. I've got a bit sick with this crash in the latest days, trying to understand the elf loader, trying toolchain configurations, etc... O:) Yours, Abel. --

I integrated this patch with our 2.6.24 kernel and it broke our APM-based battery monitor, which uses an ADC channel on the 9712. Support for this multi-function chip series seems to be in a few places; would it make sense to have one generic WM97xx driver in drivers/mfd and stack the codec, touchscreen, etc, drivers logically above (in their respective areas)? In my experience with the Wolfson series a change to the sound driver breaks touchscreen, a change to the touchscreen driver changes ADC ...