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

uses fields that do not exist otherwise.

Due to some bugs in byteorder/generic.h linux would always use C handcoded
swab64 for 64bit ntohq or cpu_to_be64.  The C version is very inefficient
and expands to 30+ instructions of horrible code.

This hurts on filesystems that use on disk big endian data structures
with 64bit data types.

This patch adds an assembly optimized swab64 to fix it. Now bswab64 is
4 instructions when your CPU supports bswap and 9 when it doesn't.
Tests were done with gcc 3.2, may be different on older gcc.

This is good for ~600 bytes code size reduction in XFS (gcc 3.2):
Before:
 503199    3296    1682  508177   7c111 fs/xfs/xfs.o
After:
 502543    3296    1682  507521   7be81 fs/xfs/xfs.o

Also should be faster.

Also some minor cleanups in the file.

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

Most of these changes have been tested and used in the 2.4 tree, so this
is mostly a forward port of 2.4 bugfixes.

* C99 initializers
* Added specific initializations instead of assuming that the private
  part of the inode is already initialized.
* Remove unused code.
* Moved container file to the struct file private data, this is to
* correct the session semantics model when file updates are fetched from
* the server (old 'sessions' shouldn't see the new container yet).
* Fixed consistency (and occasional oopes) when mmap-ing Coda files.
* Fixing up inode numbers in readdir, old libc5 getcwd was broken.
* Nuked upcall_stats, all of this can easily be maintained in userspace,
  and the existing code suffers from overflows in the fixed point
  calculations.

- Fix some printk warnings in 3c59x.c (inl() now returns a long).

- ext3 warning fix from Stephen Hemminger: "__FUNCTION__ is a
  constant and gcc warns about passing it as a mutuable string."

- Fix a return-with-BKL-held in isofs_readdir()

- paride 64-bit sector_t fix (Bill Irwin)

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

This syncs up the cyclone-timer code w/ Greg's changes from this
morning.

In the current kernels, when a PCMCIA card is inserted into or
removed from a socket, the kernel oopses because yenta_bh() tries to
dereference a NULL pointer.

The attached patch initialises the argument to yenta_bh() so that this
doesn't happen.

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

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

Add _request and _parse methods for nfsd.fh and
nfsd.exports tables.

nfsd.fh maps a filehandle-fragment to a path for a client,
and nfsd.exports maps a path to export options for a client.

a message should be:
   nfsd 10.0.1.1 {Expirydate}  domainname

if domainname is empty, then this is a NEGATIVE entry: that
IP address will be deined access.

{Expirydate} is seconds since unix epoch.
e.g.  1036105199 for midnight, halloween.

get_word understands both \x and \012 quoting styles.

This is the first upcall to actually be coded.
A request will look like:
   nfsd 127.0.0.1

This code enhances 'cache_check' to try to initiate
an up-call if the cache entry is not up-to-date, and also
defines add_word and add_hex for formating up-call
requests.  See rpc-cache.txt for more detail.

[PATCH] kNFSd: Create files: /proc/net/rpc/$CACHENAME/channel for communicating cache updates with kernel

Each cache gets it's own 'channel' at
  /proc/net/rpc/$CACHENAME/channel

Reads from the file will return all pending requests, one at a time.
select will block when at end of file.
writes will pass full lines in to be processed.

cache.c gets code to allow a 'request' to be referred pending
an update of a cache item, and revisited when the item is
updates.

svcsock.c gets code to store the relevant part of a request on deferral, and
to re-queue it when the cache item that caused the deferral is
filled in.

Rather than possibly modifying a request (as
xdr_decode_string can) we use xdr_decode_string_inplace
to symlink contents.  This string may not be nul terminated
(though it often is) so in the 'unlikely' event that is isn't
nul terminated, we copy it into a kmalloced space first.

It might be nice if vfs_symlink took a length, but then every
filesystem would have to as well....