into nuts.ninka.net:/home/davem/src/BK/net-2.5

I noticed that using extensions headers along with IPsecv6 tunnel mode did
not work in 2.5.73 + patch-2.5.73-bk3. The following patch
checks "nexthdr" instead of "iph->nexthdr" which could be an
extension header. I tested this with tunnel mode and transport mode
with and without extension headers and it worked ok.

	1. STP protocol has no security, so malcontents can fuck with the
	  bridge's topology.  The fixes are to ship with STP turned off
	  to protect the ignorant, and run STP packets through ebtables
	  netfilter for the smart.  

	  Got this one via a russian hacker "Oleg K. Artemjev" <olli@rbauto.ru>
	  before he published the paper.
	  Bridge netfilter still needs work to give a nice face on this
	  but this patch gives the hooks to filter.

	2. STP input processing was lax in it's length checking so I bet
	  you could make up a bomb packet.

	  My inspection while doing #1.

	3. Forwarding table could be abused by sending forged packets with
	   bogus source address same as the local host.  This came via
	   Lennart from Jerry Kreuscher <jerrykr@mindspring.com> who ran into
	   it by mistake.

modes. 

It used to think that IDE controllers that weren't marked as "IDE storage"
PCI class (eg CMD IDE RAID controllers mark themselves as "RAID storage")
were always using legacy mode interrupt routing, which is bogus. In fact,
the whole native vs legacy thing only makes sense for the IDE storage class,
so fix the test to match.

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

At the moment no one uses is_aligned_hugepage_range or is_hugepage_only_range,
but it is reasonable to assume they return true or false.

On error we want to return -EINVAL back to userspace.

Allow selection of boot arguments at configure time for the Motorola
ColdFire 5307 targets.

Include interrupt.h in the Motorola ColdFire PIT timer code.
Cleans up compiler warning.

Make the ROMfs copy in the startup code for Motorola M5282EVB board
conditional on actually using a ROMfs setup.

Resync with CVS. Minor update including better handling of device removal.

When show_stack() was changed to take two arguments, the use in the
voyager code was not converted.  This patch makes the correct
conversion.

These macros belong in asm-i386/scatterlist.h instead.

As the headers are disentangled this has shown up as a problem with my
MCA SCSI drivers since they no-longer include asm/pci.h in any form but
need to traverse the scatterlist.

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

Since the cs.c pcmcia core has a per-socket thread, we don't need each
socket driver having a work queue and associated complexity.

Therefore, remove this complexity and allow the socket drivers to call
pcmcia_parse_events directly from their interrupt or timer handlers.

Remove register_callback methods.  Instead, allow socket drivers
pass their events directly into cs.c via pcmcia_parse_events().

Add work-around for i82365-based socket drivers to the core PCMCIA
code.  Since insert processing is not a time critical event, we can
afford to delay (by sleeping) these for everyone.

Get/Put module when we insert and remove a card.  This avoids a
potential deadlock when socket drivers are unloaded, and we have
a cardbus card known to the system.

Move ->owner field from socket operations to pcmcia_socket.  (This
change is mainly for the SA11xx drivers, which use a core driver
for the chip, and a separate module for all the machine specific
bits.)

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

into kanga.twiddle.net:/home/rth/work/linux/axp-2.5

From Jay Estabrook:
> Here's a real short one that fixes a GENERIC build problem introduced
> in pre2, and finalizes the SABLE/LYNX support setting of HAE-4, making
> X servers finally work on those platforms.

into kernel.bkbits.net:/home/jmorris/net-2.5

into intercode.com.au:/home/jmorris/bk/net/net-2.5

Split xfrm_state_replace into xfrm_state_add and xfrm_state_replace.

Fixes:
1. Only update update lifetime and encap options if the state is valid.
2. Disallow updates to states that do not exist.
3. Bail if afinfo cannot be found.
 
This brings SADB_UPDATE in line with what is required by RFC2367.
It is also needed by SFS NAT-T support as it needs to update valid
states when the encap ports move.

I've tweaked the logic slightly so that SADB_UPDATE will fail on a
larval state that hasn't undergone SADB_GETSPI.  This is what RFC2367
calls for and it simplifies the code in that we don't have to call
find_acq for SADB_UPDATE.

This doesn't affect any of the three KMs as they either don't use
SADB_UPDATE or call SADB_GETSPI before doing an update.

The source address of an SA is not necessarily equal to the source address
in the selector.  This patch addresses this problem.