linux-toradex.git/kernel, branch v2.6.19.2

[PATCH] sched: remove __cpuinitdata anotation to cpu_isolated_map

2007-01-10T19:05:18+00:00

The structure cpu_isolated_map is used not only during initialization.
Multi-core scheduler configuration changes and exclusive cpusets
use this during run time.  During setting of sched_mc_power_savings
 policy, this structure is accessed to update sched_domains.

Signed-off-by: Tim Chen 
Acked-by: Suresh Siddha 
Acked-by: Ingo Molnar 
Signed-off-by: Chris Wright

[PATCH] softirq: remove BUG_ONs which can incorrectly trigger

2006-12-11T19:32:40+00:00

It is possible to have tasklets get scheduled before softirqd has had a chance
to spawn on all CPUs.  This is totally harmless; after success during action
CPU_UP_PREPARE, action CPU_ONLINE will be called, which immediately wakes
softirqd on the appropriate CPU to process the already pending tasklets.  So
there is no danger of having a missed wakeup for any tasklets that were
already pending.

In particular, i386 is affected by this during startup, and is visible when
using a very large initrd; during the time it takes for the initrd to be
decompressed, a timer IRQ can come in and schedule RCU callbacks.  It is also
possible that resending of a hardware IRQ via a softirq triggers the same bug.

Because of different timing conditions, this shows up in all emulators and
virtual machines tested, including Xen, VMware, Virtual PC, and Qemu.  It is
also possible to trigger on native hardware with a large enough initrd,
although I don't have a reliable case demonstrating that.

Signed-off-by: Zachary Amsden 
Cc: 
Cc: Ingo Molnar 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Chris Wright

[PATCH] PM: Fix swsusp debug mode testproc

2006-12-11T19:32:40+00:00

The 'testproc' swsusp debug mode thaws tasks twice in a row, which is _very_
confusing.  Fix that.

Signed-off-by: Rafael J. Wysocki 
Acked-by: Pavel Machek 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Chris Wright

Merge branch 'for-linus' of git://one.firstfloor.org/home/andi/git/linux-2.6

2006-11-29T01:28:41+00:00

* 'for-linus' of git://one.firstfloor.org/home/andi/git/linux-2.6:
  [PATCH] x86-64: Use stricter in process stack check for unwinder
  [PATCH] i386: Fix compilation with UP genericarch
  [PATCH] x86-64: Fix warning in io_apic.c
  [PATCH] x86-64: work around gcc4 issue with -Os in Dwarf2 stack unwind
  [PATCH] x86_64: Align data segment to PAGE_SIZE boundary

[PATCH] fix create_write_pipe() error check

2006-11-29T01:26:50+00:00

The return value of create_write_pipe()/create_read_pipe() should be
checked by IS_ERR().

Signed-off-by: Akinobu Mita 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] x86-64: work around gcc4 issue with -Os in Dwarf2 stack unwind

2006-11-28T19:12:59+00:00

This fixes a problem with gcc4 mis-compiling the stack unwind code under
-Os, which resulted in 'stuck' messages whenever an assembly routine was
encountered.

(The second hunk is trivial cleanup.)

Signed-off-by: Jan Beulich

[PATCH] lockdep: spin_lock_irqsave_nested()

2006-11-25T21:28:34+00:00

Introduce spin_lock_irqsave_nested(); implementation from:
 http://lkml.org/lkml/2006/6/1/122
Patch from:
 http://lkml.org/lkml/2006/9/13/258

[akpm@osdl.org: two compile fixes]
Signed-off-by: Arjan van de Ven 
Signed-off-by: Jiri Kosina 
Signed-off-by: Peter Zijlstra 
Acked-by: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] fix copy_process() error check

2006-11-25T21:28:34+00:00

The return value of copy_process() should be checked by IS_ERR().

Signed-off-by: Akinobu Mita 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

Don't call "note_interrupt()" with irq descriptor lock held

2006-11-22T17:32:06+00:00

This reverts commit f72fa707604c015a6625e80f269506032d5430dc, and solves
the problem that it tried to fix by simply making "__do_IRQ()" call the
note_interrupt() function without the lock held, the way everybody else
does.

It should be noted that all interrupt handling code must never allow the
descriptor actors to be entered "recursively" (that's why we do all the
magic IRQ_PENDING stuff in the first place), so there actually is
exclusion at that much higher level, even in the absense of locking.

Acked-by: Vivek Goyal 
Acked-by:Pavel Emelianov 
Cc: Andrew Morton 
Cc: Ingo Molnar 
Cc: Adrian Bunk 
Signed-off-by: Linus Torvalds

[PATCH] lockdep: fix static keys in module-allocated percpu areas

2006-11-17T19:10:37+00:00

lockdep got confused by certain locks in modules:

 INFO: trying to register non-static key.
 the code is fine but needs lockdep annotation.
 turning off the locking correctness validator.

 Call Trace:
  [] dump_trace+0xaa/0x3f2
  [] show_trace+0x3a/0x60
  [] dump_stack+0x15/0x17
  [] __lock_acquire+0x724/0x9bb
  [] lock_acquire+0x4d/0x67
  [] rt_spin_lock+0x3d/0x41
  [] :ip_conntrack:__ip_ct_refresh_acct+0x131/0x174
  [] :ip_conntrack:udp_packet+0xbf/0xcf
  [] :ip_conntrack:ip_conntrack_in+0x394/0x4a7
  [] nf_iterate+0x41/0x7f
  [] nf_hook_slow+0x64/0xd5
  [] ip_rcv+0x24e/0x506
  [...]

Steven Rostedt found the bug: static_obj() check did not take
PERCPU_ENOUGH_ROOM into account, so in-module DEFINE_PER_CPU-area locks
were triggering this message.

Signed-off-by: Ingo Molnar 
Signed-off-by: Steven Rostedt 
Signed-off-by: Linus Torvalds