From: "William A.(Andy) Adamson" <andros@citi.umich.edu>

From: "William A.(Andy) Adamson" <andros@citi.umich.edu>

Put all clients in a LRU list and use a "work_queue" to
expire old clients periodically.

From: "William A.(Andy) Adamson" <andros@citi.umich.edu>

When readdir is enumerating a directory and finds a mountpoint,
it needs to do a bit of extra work to find the filehandle to be
returned in the readdir reply.

It is even possible that finding the filehandle requires an up-call,
so the request might be dropped to be re-tried later.

From: Hirokazu Takahashi <taka@valinux.co.jp>

In svc_tcp_listen_data_ready we should be waiting for
TCP_LISTEN, not TCP_ESTABLISHED.  The later only worked
by accident.

Also, if a socket is closed as soon as we accept it, we
must shut it down straight away as we will never get a 'close'
event.

The most significant fix is cleaning up properly when
nfs service is stopped.

Also fix some refcounting problems and other little bits.

svc_pushback_unused_pages must be ready of the possibility that
no pages were allocated or will need to be pushed back.

From Adrian Bunk.

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

Here enclosed an update for the new IRQ and module_param APIs.
eata.h and u14-34f.h are no longer used and will be deleted.

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

The parisc ports may use both the lasi700 and sim710 versions of this driver
Unfortunately, one must be memory mapped, and one must be IO mapped, so
add code to the driver for this case

into kernel.bkbits.net:/home/davem/sparc-2.5

into kernel.bkbits.net:/home/davem/sparc-2.5

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

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

Some socket hardware appears to "bounce" when a card is inserted - we
seem to receive more than one SS_DETECT event.  Unfortunately, this
causes us to initialise, setup the socket, and create the necessary
devices multiple times.

Fix this by ignoring card insertion events when we already know that
there is a card in the socket.

while trying to access a disk drive via an FCP bridge we got an FCP_RSP IU
with the RSP_CODE field set to "FCP_CMND Fields Invalid". This happened
after sending a START_STOP command to the device. Reason for this was that
the FCP_CMND IU incorrectly had the RDDATA field set to one, because of a
bug in sd_spinup_disk(). There the data direction for START_STOP is set
to SCSI_DATA_READ instead of SCSI_DATA_NONE.
Please apply the patch below.

Thanks,
Heiko

The attached patch fixes the compile errors in inia100.c described in
Bugzilla bug #345 at http://bugme.osdl.org/show_bug.cgi?id=345. It was
built against 2.5.71. I do not have the hardware, so I have only
verified that it compiles correctly.

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

Which is 0.1% of the times, I'll have to research usage and eventually
kill this uglymoron that is responsible for 9 out of 10 "ipx is not
working with mars_nwe, why?" answer "Disable the damn CONFIG_IPX_INTERN
and be happy!" Thanks to Geert for reporting thisn in lkml.

Move it to the protocols that we're using this pointers for other
purposes than a list pointer as the name implies, namely tcp and
sctp, where they are used as a pointer to the bind_hash. Shrink,
struct sock, shrink! :-)

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

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

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

Don't remove sillyrenamed files: those will be removed (by
nfs_async_unlink) when they are no longer used any more.

Remove double initialization of "i_mode" in __nfs_fhget().

DM originally stored a devfs handle in the hash-cell, and performed the
unregister based on that handle. These devfs handles have since been removed,
and devices are registered and unregistered simply based on their names. So
the device now needs to be unregistered before we lose the name.

See the following BK change for more details:
http://linux.bkbits.net:8080/linux-2.5/diffs/drivers/md/dm-ioctl.c@1.6?nav=index.html|src/|src/drivers|src/drivers/md|hist/drivers/md/dm-ioctl.c
[Kevin Corry]

We must always allocate windows below 1MB when a socket driver
indicates that it does not have "page registers".  Handle this
case in rsrc_mgr.c within find_mem_region rather than each use
of find_mem_region().

Remove the racy check_mem_resource() function.  Instead, claim
the region while we check it, passing a resource structure to
the core validation functions.

The overwhelming majority of Linux users are using modular PCMCIA,
and loading the "yenta_socket" module.  2.5.71 unfortunately changed
the name to "yenta" when pci_socket.c was combined with yenta.c.
Rename yenta.[ch] to yenta_socket.[ch] for compatibility.