this change:  Jim Wilson says that gcc v3.3 also supports
	marking ar.pfs as clobbered, so use ia64_spinlock_contention()
	for any GCC with v3.3 or newer.

	CONFIG_DISABLE_VHPT.

	put_user() arguments with function-calls would cause the
	macro to return unexpected values.  Fixed by avoiding macro
	argument evaluation while r8/r9 are in use for exception-handling
	purposes.  Also, consolidated access-macros so that GCC and
	Intel compiler use 90% the same code.

	atomic_dec_and_lock().  Actually, this could be the generic
	version for any platform that has cmpxchg().

	backwards-compatibility with older (broken) versions of GCC which
	recognize a signal-handler only if it is in the address range
	from 0xa000000000000100. to 0xa000000000020000.

	clobbered, so use ia64_spinlock_contention() for any GCC with
	v3.3 or newer.

Here's a  fix for non-preemption safety in perfmon.c.

I haven't tried it while running a preemption stress test, but this
allows q-syscollect to work.

The security init section was incorrectly using PAGE_OFFSET instead of
LOAD_OFFSET.

Here is a new improved patch for verifying user access to string
passed in to kernel on write to /proc/irq/<pid>/smp_affinity.

The access_ok() but missing __get_user() on each byte earlier patch
has been replaced with a copy_from_user().

I have built it and verified that it handles write requests
as before, on an ia64 system (well - you can no longer pass
more than 14 spaces after the 'R' - tough).

	across a signal trampoline (in user space).  Reported by
	Laurent Morichetti.

I've got a lot more changes than what's included here.  I've put this
down to the bear minimum to get things working sanely.

Mainly, I just want to get all the people hit by this a chance to use
2.6.0 without having to get our tree. Changes itemized:

 - Fix deadlock possibility in csr.c:read_maps()
 - Fix kmalloc to use ATOMIC in highlevel.c.
 - s/in_interrupt/irqs_disabled/ in ieee1394_transactions.c to fix
   warnings when transactions occured.
 - Introduce a release callback for the host driver and use it correctly.
 - Reorganize the nodemgr probe so we do an initial scan to discover
   devices, check IRM/CycleMaster, then do a final full probe when things
   are kosher. Fixes a problem where device registration and hotplug
   would cause some serious problems when a bus reset was forced in the
   middle of the probe.

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

into home.osdl.org:/home/torvalds/v2.5/linux

There are /proc handles there setup by proc_tty_register_driver, but there is
no module ownership association, so anything that reads after module unload
will blow.

The trivial fix is to propagate the owner of tty_driver to proc entry.

This fixes a small, but important bug in smsc-ircc2.c.

Without this the driver tries release the same region twice.

      Tracked down by Rohit Seth.

Do not special case ENOMEM as an error code, we should free up
the packet for all errors.

Most of the breakage came from cset 1.838.10.3

The br_netfilter_{init,fini}() calls need to be guarded by
BRIDGE_NETFILTER, from Michal Janusz Miroslaw.

When bringing an interface down do not forget to clear the
IF_RS_SENT and IF_RA_RCVD flags.

into home.osdl.org:/home/torvalds/v2.5/linux

This fixes an oops that can occur if JFS is used as the root filesystem.

Writes to a device node may cause a ->write_inode to be called during a
read-only mount.  JFS needs to check for NULL log in jfs_flush_journal. 

into home.osdl.org:/home/torvalds/v2.5/linux

Also, make sure NET_RX_DROP is returned if we did not accept the
packet.

In implementations that use no socket locking, such as RAW sockets,
once we queue the SKB to the socket another cpu can remove the SKB
from the socket queue and free up the SKB making the skb->len access
touch freed memory.

Based upon a report from Burton Windle, kernel bugzilla #937

into home.osdl.org:/home/torvalds/v2.5/linux

Also add some ServerWorks-specific tweaks.

into redhat.com:/spare/repo/libata-2.5

All the users of this function in the SCSI tree call it with the host
lock held.  With the new list traversal code, it was trying to take
the lock again to traverse the list.

Fix it to use the unlocked version of list traversal and modify the
header comments to make it clear that the lock is expected to be held
on calling it.

Noted by Harald Welte (laforge@netfilter.org)

into home.osdl.org:/home/torvalds/v2.5/linux