This fixes several trivial bounds/limits errors that were pointed out by
the Stanford Checker.

This fixes a potential divide-by-zero found by the Stanford Checker.

Patch from Marc Zyngier <mzyngier@freesurf.fr>

My previous round of EISA hacking left the 3c59x driver unable to
compile on non-PCI systems (that is, EISA only...).

This small patch fixes it.

Patch from Marc Zyngier <mzyngier@freesurf.fr>

Fix compilation of 3c509.c

Patch from: Eric Lammerts <eric@lammerts.org>

Every time you do a loop mount, a kernel thread is started (those
processes are called "loop0", "loop1", etc.). The problem is that when
it starts, it's counted as one of your processes. Then, it's
changed to be a root-owned process without correcting that count.

Patch below fixes the problem. It moves the bookkeeping of changing
current->user to a new function switch_uid() (which is now also used
by exec_usermodehelper() in kmod.c). The patch is tested.

mempools have the wrong semantics for use by buffer_heads.  The problem
scenario:

- Process A calls mempool_alloc(), asking for a buffer_head.

- While process A sleeps, process B frees up a ton of memory.

That's it.  There is no longer any memory pressure, so nobody frees any
buffer_heads, so process A does not get woken up.  I managed to trigger this
in some testing recently.

One approach would be to use a schedule_timeout(2) in mempool_alloc().

Anyway, the importance of buffer_head allocation was lessened when swapout
stopped using them, so let's just drop the mempool out of it for now.

A very long time ago ext3_fill_super() was beng called under the VFS's
lock_super(), and it had to drop that lock for deadlock avoidance reasons.

But the VFS was later changed to not take lock_super() across ->fill_super(),
so we're upping a non-downed semaphore.

Just take it out.

Redo the (strange) layout of some of Roger's comments.

Patch from: Szabolcs Berecz <szabi@mplayerhq.hu>

No need to check root->rnode in the loop. In the loop it remains nonzero.

We need to validate that the address and length of a MAP_FIXED request are
suitable for hugetlb pages.

Patch from James Curbo <phoenix@sandwich.net>

The amd74xx IDE driver in 2.5.59 has support for the nforce IDE controller,
but not explicitly for the nforce2 IDE controller (which has a different PCI
ID, which is in the kernel already).  I'm not sure if the nforce and nforce2
controllers are identical, but I made a small patch that made the amd74xx
driver recognize the nforce2 IDE, and it boots for me, seems to work fine, as
my drives were tuned to their highest transfer rate automatically (udma5).

I don't know if this patch is proper or correct, but it Works for Me [tm].
Patch is attached.

Vojtech has acked this change.

(I asked Dave for this...)

From: Dave Olien <dmo@osdl.org>

Add me as maintainer for DAC960 driver.

Patch from Dave Olien <dmo@osdl.org>

This was found by the Standford Checker.
The LogicalDeviceNumber bad range test was changed from > to >=
I also replaced a couple of panic() calls with error messages,
since panic-ing seemed a little extreme.

journal_try_start() is a function which nonblockingly attempts to open a JBD
transaction handle.  It was added a long time ago when there were concerns
that ext3_writepage() could block kswapd for too long.

It was never clearly necessary.

So the patch throws it all away and just calls the blocking journal_start()
from ext3_writepage().

Patch from William Lee Irwin III <wli@holomorphy.com>

Don't touch IO-APIC physid's on NUMA-Q. The BIOS pre-programs them.

Patch from Ravikiran G Thirumalai <kiran@in.ibm.com>

Converts the ia32 kernel profiler to use use the percpu area infrastructure.

uninline get_jiffies_64() for 32-bit architectures

Part of the bounds checking bugs found by the Stanford checker.

The 4 fixes below have been acked by their maintainers.

Move the definition of version[] down to where __initdata has been defined.

Patch from Joel Becker <Joel.Becker@oracle.com>

The task_struct->sig -> task_struct->signal bits.

Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz> points out a bug in
ll_rw_block() usage.

Typical usage is:

	mark_buffer_dirty(bh);
	ll_rw_block(WRITE, 1, &bh);
	wait_on_buffer(bh);

the problem is that if the buffer was locked on entry to this code sequence
(due to in-progress I/O), ll_rw_block() will not wait, and start new I/O.  So
this code will wait on the _old_ I/O, and will then continue execution,
leaving the buffer dirty.

It turns out that all callers were only writing one buffer, and they were all
waiting on that writeout.  So I added a new sync_dirty_buffer() function:

	void sync_dirty_buffer(struct buffer_head *bh)
	{
		lock_buffer(bh);
		if (test_clear_buffer_dirty(bh)) {
			get_bh(bh);
			bh->b_end_io = end_buffer_io_sync;
			submit_bh(WRITE, bh);
		} else {
			unlock_buffer(bh);
		}
	}

which allowed a fair amount of code to be removed, while adding the desired
data-integrity guarantees.

UFS has its own wrappers around ll_rw_block() which got in the way, so this
operation was open-coded in that case.

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart-respin

This removes lots of annoying problems trying to prevent both modules
from being loaded, and also shares quite a bit of code.
CONFIG_AGP3 will disable AGP3 mode operation of KT400s.

Based upon information from VIA, this also adds a bunch of placeholder
entries that will get filled in over time when they have been proven
to work with the code with no extra modification.

  
The AGP3 spec allows for >1 AGP bus. This is the first of several patches
from Jeff Hartmann towards a context-using agp_bridge, by replacing
agp_bridge.foo accesses with agp_bridge->foo accesses. For now, there
should be no functional differences, as there is still only a single
agp_bridge_data struct defined.