Clear up the code around  start_sem so it's more obvious, and remove a pointless
down/up pair on buffer_sem (shutdown is already synchronised in sync_stop()).

Consolidate all the arch copies of timer_int.c into one place. Also fixes
a problem with PA-RISC not using instruction_pointer() when it should.

Convention is that error returns are negative.

Cset exclude: akpm@digeo.com|ChangeSet|20030204165956|06074
Cset exclude: akpm@digeo.com|ChangeSet|20030204165949|06077

into home.transmeta.com:/home/torvalds/v2.5/linux

This patch adds new PCI IDs to the drivers/pci/pci.ids file.

into home.transmeta.com:/home/torvalds/v2.5/linux

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

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

- Consistent naming (i.e. jhash_xxx)
- Reduces the 2&1 word variants to call jhash_3words()
- Replaces __inline__ with inline.

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

Using sk_set_owner and having THIS_MODULE in the struct proto_ops
registered with the core. The sk_set_owner cases are in the callers
of tp->af_specific->syn_recv_sock so as to not have spurious extra
sk_set_owner calls in the ipv6 code that reuses ipv4 code.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops
registered with the core, also remove the MOD_{INC,DEC}_USE_COUNT,
as they are not needed anymore with this new net module infrastructure
for struct sock and struct socket. (well, see the netdev discussion :)

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered
with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered
with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered
with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered
with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered
with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered
with the core.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered
with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using THIS_MODULE in the struct proto_ops registered with the core.

Using sk_set_owner and having THIS_MODULE in the struct proto_ops registered 
with the core.

As per discussions in netdev we'll probably be moving to a brand new scheme, but this
set of changesets have been discussed and are an improvement to the current situation
and were already done prior to this thread happening.

Several hash table implementations in the networking were
remotely exploitable.  Remote attackers could launch attacks
whereby, using carefully choosen forged source addresses, make
every routing cache entry get hashed into the same hash chain.

Netfilter's IP conntrack module and the TCP syn-queue implementation
had identical vulnerabilities and have been fixed too.

The choosen solution to the problem involved using Bob's Jenkins
hash along with a randomly choosen input.  For the ipv4 routing
cache we take things one step further and periodically choose a
new random secret.  By default this happens every 10 minutes, but
this is configurable by the user via sysctl knobs.