From: <gerg@snapgear.com>

Add start up code specific to the newly added COBRA5282 board.

From: <gerg@snapgear.com>

Fixes to the Motorola ColdFire 5282 setup code:

. fix interrupt routine return types to be irqreturn_t
. add DMA base addresses array

From: <gerg@snapgear.com>

Add startup code specific to newly supported COBRA5272 board.

From: <gerg@snapgear.com>

Allow for auto-detecting the size of the DRAM in the startup code for the
Motorola/5272 (ColdFire) board.  Use the DRAM sizing register, since it will
have been setup by the debug boot monitor (dBUG).

From: <gerg@snapgear.com>

Add type field to printk calls in m68knommu timers.c

From: <gerg@snapgear.com>

Define the DMA register set base address array for those m68knommu/ColdFire
CPU's that have a DMA engines.

From: <gerg@snapgear.com>

Add type field to printk calls in m68knommu mm/init.c.  Patch originally
from kernel janitors.

From: <gerg@snapgear.com>

Add type field to printk calls.  Patch original provided by kernel
janitors.

From: <gerg@snapgear.com>

Add build support for the senTec vendor to m68knommu architecture Makefile.

From: <gerg@snapgear.com>

Fix architecture/cpu defines to support those used by modern versions of
gcc (that is gcc > 3.3.x) for m68knommu.  The standard for defining
ColdFire architectures is no longer __mcf5200__, it is now __mcoldfire__.
This patch fixes all the occurances in the m68knommu/lib functions.

From: <gerg@snapgear.com>

A couple of additions to the linker script for m68knommu platforms:

. add support for COBRA5272 and COBRA5282 boards
. link in .rodata.str1 generated by gcc-3.3.x compilers

From: <gerg@snapgear.com>

Add type to all printk calls in m68knommu traps.c.  Also added a modern
dump_stack function.

From: <gerg@snapgear.com>

Cleanup m68knommu/kernel/setup.c.  Add type to all printk calls, remove
obsolete framebuffer setup and fix a few irqreturn_t for interrupt handlers
in prototypes.

Printk cleanup originally from kernel janitors.

From: <gerg@snapgear.com>

Add local m68knommu dma allocation code to build list.

From: <gerg@snapgear.com>

Create the coherent DMA allocation functions for m68knommu.  No current
hardware in this class requires anything special, so it just just does
normal allocations after sanity checks.

From: <gerg@snapgear.com>

Cleanup m68knommu's comempci.c support code.  Add type to all printk calls.
Patch originally from kernel janitors.

From: <gerg@snapgear.com>

A few changes to the m68knommu Kconfig:

. Add support for 64MHz clocked CPU's
. Add support for selecting the COBRA5272 and COBRA5282 boards
. Use drivers/Kconfig for driver configuration
. Allow configuring compilation with frame-pointer

From: <gerg@snapgear.com>

Some kernel janitor clean ups of printk for the m68knommu specific process
code.

And more importantly a fix to the kernel_thread() asm code to correctly
return the pid back to the return var from the clone system call.

From: <gerg@snapgear.com>

Create a dma-mapping.h for m68knommu architecture.

From: <miles@mcspd15.ucom.lsi.nec.co.jp> (Miles Bader)

Is this something that should be done in <asm-generic/dma-mapping.h>?

From: <miles@mcspd15.ucom.lsi.nec.co.jp> (Miles Bader)

Otherwise the compiler can delete them (this is one of those "how on earth
did it ever work before" moments).

From: Roland McGrath <roland@redhat.com>

The posix-timers implementation associates timers with the creating thread
and destroys timers when their creator thread dies.  POSIX clearly
specifies that these timers are per-process, and a timer should not be torn
down when the thread that created it exits.  I hope there won't be any
controversy on what the correct semantics are here, since POSIX is clear
and the Linux feature is called "posix-timers".

The attached program built with NPTL -lrt -lpthread demonstrates the bug.
The program is correct by POSIX, but fails on Linux.  Note that a until
just the other day, NPTL had a trivial bug that always disabled its use of
kernel timer syscalls (check strace for lack of timer_create/SYS_259).  So
unless you have built your own NPTL libs very recently, you probably won't
see the kernel calls actually used by this program.

Also attached is my patch to fix this.  It (you guessed it) moves the
posix_timers field from task_struct to signal_struct.  Access is now
governed by the siglock instead of the task lock.  exit_itimers is called
from __exit_signal, i.e.  only on the death of the last thread in the
group, rather than from do_exit for every thread.  Timers' it_process
fields store the group leader's pointer, which won't die.  For the case of
SIGEV_THREAD_ID, I hold a ref on the task_struct for it_process to stay
robust in case the target thread dies; the ref is released and the dangling
pointer cleared when the timer fires and the target thread is dead.  (This
should only come up in a buggy user program, so noone cares exactly how the
kernel handles that case.  But I think what I did is robust and sensical.)

/* Test for bogus per-thread deletion of timers.  */

#include <stdio.h>
#include <error.h>
#include <time.h>
#include <signal.h>
#include <stdint.h>
#include <sys/time.h>
#include <sys/resource.h>
#include <unistd.h>
#include <pthread.h>

/* Creating timers in another thread should work too.  */
static void *do_timer_create(void *arg)
{
	struct sigevent *const sigev = arg;
	timer_t *const timerId = sigev->sigev_value.sival_ptr;
	if (timer_create(CLOCK_REALTIME, sigev, timerId) < 0) {
		perror("timer_create");
		return NULL;
	}
	return timerId;
}

int main(void)
{
	int i, res;
	timer_t timerId;
	struct itimerspec itval;
	struct sigevent sigev;

	itval.it_interval.tv_sec = 2;
	itval.it_interval.tv_nsec = 0;
	itval.it_value.tv_sec = 2;
	itval.it_value.tv_nsec = 0;

	sigev.sigev_notify = SIGEV_SIGNAL;
	sigev.sigev_signo = SIGALRM;
	sigev.sigev_value.sival_ptr = (void *)&timerId;

	for (i = 0; i < 100; i++) {
		printf("cnt = %d\n", i);

		pthread_t thr;
		res = pthread_create(&thr, NULL, &do_timer_create, &sigev);
		if (res) {
			error(0, res, "pthread_create");
			continue;
		}
		void *val;
		res = pthread_join(thr, &val);
		if (res) {
			error(0, res, "pthread_join");
			continue;
		}
		if (val == NULL)
			continue;

		res = timer_settime(timerId, 0, &itval, NULL);
		if (res < 0)
			perror("timer_settime");

		res = timer_delete(timerId);
		if (res < 0)
			perror("timer_delete");
	}

	return 0;
}

From: Yoshinori Sato <ysato@users.sourceforge.jp>

- add Kconfig depends H8300
- H8/300 support compile error fixed.

From: Yoshinori Sato <ysato@users.sourceforge.jp>

- fix any error/warning
- fix {request,freee}_irq interrupt control fix
- add dump_stack
- fix show_trace_task
- fix typo

From: Yoshinori Sato <ysato@users.sourceforge.jp>

- use new serial driver (drivers/serial/sh-sci.[ch])
- typo fix
- add message level

From: Yoshinori Sato <ysato@users.sourceforge.jp>

- cleanup define

From: Yoshinori Sato <ysato@users.sourceforge.jp>

- fix PTRACE_SIGLESTEP bug.
- separate to CPU depend.

From: "Randy.Dunlap" <rddunlap@osdl.org>

Use x86 EFLAGS defines in place of hardwired constants.

From: Arjan van de Ven <arjanv@redhat.com>

isdn: dynamically allocate big structures

From: Arjan van de Ven <arjanv@redhat.com>

ide.c: constant array of strings can be static

From: Arjan van de Ven <arjanv@redhat.com>

ide-cd: a few 512 byte scratch buffers can be static; they are just for
putting "padding" sectors in that aren't used.

(acked by Jens)

From: Julie DeWandel <jdewand@redhat.com>

A problem exists where a 32-bit application can have a huge bss, one that
is so large that an overflow of the TASK_SIZE happens.  But in this case,
the overflow is not detected in load_elf_binary().  Instead, because
arithmetic is being done using 32-bit containers, a truncation occurs and
the program gets loaded when it shouldn't have been.  Subsequent execution
yields unpredictable results.

The attached patch fixes this problem by checking for the overflow
condition and sending a SIGKILL to the application if the overflow is
detected.  This problem can in theory exist when loading the elf
interpreter as well, so a similar check was added there.

From: Fabian Frederick <Fabian.Frederick@skynet.be>

Here's a trivial patch to avoid definition redundancy in es1688.

- Don't leak a pathname ref on error

- Don't do putname() on a nameidata.

From: Brian Gerst <bgerst@didntduck.org>

- Move empty_zero_page and swapper_pg_dir to BSS.  This requires that BSS
  is cleared earlier, but reclaims over 3k that was lost due to page
  alignment.

- Move stack_start, ready, and int_msg, boot_gdt_descr, idt_descr, and
  cpu_gdt_descr to .data.  They were interfering with disassembly while in
  .text.

unmap_vmas() will cause scheduling latency when tearing down really big vmas
on !CONFIG_PREEMPT.  That's a bit unkind to the non-preempt case, so let's do
a cond_resched() after zapping 1024 pages.

From: Bernhard Rosenkraenzer <bero@arklinux.org>

mixart.h uses tasklet_struct without including linux/interrupt.h -- fix
attached.

From: Stephen Smalley <sds@epoch.ncsc.mil>

This patch drops the ratelimit code from the SELinux avc, as this can now
be handled by the audit framework.  Enabling and setting the ratelimit is
then left to userspace.

From: Stephen Smalley <sds@epoch.ncsc.mil>

This patch changes an error message printk'd by security_compute_sid to use
the audit framework instead.  These errors reflect situations where a
security transition would normally occur due to policy, but the resulting
security context is not valid.  The patch also changes the code to always
call the audit framework rather than only doing so when permissive as this
was causing problems with testing policy, and does some code cleanup.

From: James Morris <jmorris@redhat.com>

This patch makes the IPv6 code work with the audit framework, following the
merge of both.