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

fix section mismatch warning in lockdep

2007-03-09T18:50:31+00:00

lockdep_init() is marked __init but used in several places
outside __init code. This causes following warnings:
$ scripts/mod/modpost kernel/lockdep.o
WARNING: kernel/built-in.o - Section mismatch: reference to .init.text:lockdep_init from .text.lockdep_init_map after 'lockdep_init_map' (at offset 0x105)
WARNING: kernel/built-in.o - Section mismatch: reference to .init.text:lockdep_init from .text.lockdep_reset_lock after 'lockdep_reset_lock' (at offset 0x35)
WARNING: kernel/built-in.o - Section mismatch: reference to .init.text:lockdep_init from .text.__lock_acquire after '__lock_acquire' (at offset 0xb2)

The warnings are less obviously due to heavy inlining by gcc - this is not
altered.

Fix the section mismatch warnings by removing the __init marking, which
seems obviously wrong.

Signed-off-by: Sam Ravnborg 
Acked-by: Ingo Molnar 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

kernel/time/clocksource.c needs struct task_struct on m68k

2007-03-09T18:50:30+00:00

kernel/time/clocksource.c needs struct task_struct on m68k.

Because it uses spin_unlock_irq(), which, on m68k, uses hardirq_count(), which
uses preempt_count(), which needs to dereference struct task_struct, we
have to include sched.h. Because it would cause a loop inclusion, we
cannot include sched.h in any other of asm-m68k/system.h,
linux/thread_info.h, linux/hardirq.h, which leaves this ugly include in
a C file as the only simple solution.

Signed-off-by: Mathieu Desnoyers 
Cc: Ingo Molnar 
Cc: Roman Zippel 
Cc: Thomas Gleixner 
Signed-off-by: Andrew Morton 
Signed-off-by: Greg Kroah-Hartman

sched: fix SMT scheduler bug

2007-03-09T18:50:27+00:00

The SMT scheduler incorrectly skips kernel threads even if they are
runnable (but they are preempted by a higher-prio user-space task which got
SMT-delayed by an even higher-priority task running on a sibling CPU).

Fix this for now by only doing the SMT-nice optimization if the
to-be-delayed task is the only runnable task.  (This should cover most of
the real-life cases anyway.)

This bug has been in the SMT scheduler since 2.6.17 or so, but has only
been noticed now by the active check in the dynticks code.

Signed-off-by: Ingo Molnar 
Cc: Michal Piotrowski 
Cc: Nick Piggin 
Cc: Thomas Gleixner 
Cc: Chuck Ebbert 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

swsusp: Fix possible oops in userland interface

2007-03-09T18:50:24+00:00

Fix the Oops occuring when SNAPSHOT_PMOPS or SNAPSHOT_S2RAM ioctl is called on
a system without pm_ops defined (eg. a non-ACPI kernel on x86 PC).

Signed-off-by: Stefan Seyfried 
Signed-off-by: Rafael J. Wysocki 
Acked-by: Pavel Machek 
Signed-off-by: Greg Kroah-Hartman

Fix posix-cpu-timer breakage caused by stale p->last_ran value

2007-03-09T18:50:24+00:00

Problem description at:
http://bugzilla.kernel.org/show_bug.cgi?id=8048

Commit b18ec80396834497933d77b81ec0918519f4e2a7 
    [PATCH] sched: improve migration accuracy
optimized the scheduler time calculations, but broke posix-cpu-timers.

The problem is that the p->last_ran value is not updated after a context
switch. So a subsequent call to current_sched_time() calculates with a
stale p->last_ran value, i.e. accounts the full time, which the task was
scheduled away.

Signed-off-by: Thomas Gleixner 
Acked-by: Ingo Molnar 
Signed-off-by: Greg Kroah-Hartman

[PATCH] fork_idle() should be cpuinit, not devinit

2007-02-02T00:17:06+00:00

Signed-off-by: Al Viro 
Signed-off-by: Linus Torvalds

[PATCH] kprobes: replace magic numbers with enum

2007-01-31T00:01:35+00:00

Replace the magic numbers with an enum, and gets rid of a warning on the
specific architectures (ex.  powerpc) on which the compiler considers
'char' as 'unsigned char'.

Signed-off-by: Masami Hiramatsu 
Cc: Prasanna S Panchamukhi 
Cc: Ananth N Mavinakayanahalli 
Cc: Anil S Keshavamurthy 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] namespaces: fix task exit disaster

2007-01-30T21:40:36+00:00

This is based on a patch by Eric W.  Biederman, who pointed out that pid
namespaces are still fake, and we only have one ever active.

So for the time being, we can modify any code which could access
tsk->nsproxy->pid_ns during task exit to just use &init_pid_ns instead,
and move the exit_task_namespaces call in do_exit() back above
exit_notify(), so that an exiting nfs server has a valid tsk->sighand to
work with.

Long term, pulling pid_ns out of nsproxy might be the cleanest solution.

Signed-off-by: Eric W. Biederman 

[ Eric's patch fixed to take care of free_pid() too ]

Signed-off-by: Serge E. Hallyn 
Signed-off-by: Linus Torvalds

Revert "[PATCH] namespaces: fix exit race by splitting exit"

2007-01-30T21:35:18+00:00

This reverts commit 7a238fcba0629b6f2edbcd37458bae56fcf36be5 in
preparation for a better and simpler fix proposed by Eric Biederman
(and fixed up by Serge Hallyn)

Acked-by: Serge E. Hallyn 
Signed-off-by: Linus Torvalds

[PATCH] namespaces: fix exit race by splitting exit

2007-01-30T16:26:44+00:00

Fix exit race by splitting the nsproxy putting into two pieces.  First
piece reduces the nsproxy refcount.  If we dropped the last reference, then
it puts the mnt_ns, and returns the nsproxy as a hint to the caller.  Else
it returns NULL.  The second piece of exiting task namespaces sets
tsk->nsproxy to NULL, and drops the references to other namespaces and
frees the nsproxy only if an nsproxy was passed in.

A little awkward and should probably be reworked, but hopefully it fixes
the NFS oops.

Signed-off-by: Serge E. Hallyn 
Cc: Herbert Poetzl 
Cc: Oleg Nesterov 
Cc: "Eric W. Biederman" 
Cc: Cedric Le Goater 
Cc: Daniel Hokka Zakrisson 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds