Commits · d7e95acde63cabed2ab9075d1979b1c82cea252a · nexedi / linux

24 Aug, 2004 1 commit

[IPV6]: Fix device handling in ip6_route_add(). · d7e95acd

Hideaki Yoshifuji authored Aug 23, 2004

Signed-off-by: HIDEAKI Yoshifuji <yoshfuji@linux-ipv6.org>
Signed-off-by: David S. Miller <davem@redhat.com>

d7e95acd

23 Aug, 2004 39 commits

Linux 2.6.9-rc1 · 5a528e75
Linus Torvalds authored Aug 23, 2004

5a528e75

[PATCH] ppc64: use struct list_head for hose_list · fae337c7

Paul Mackerras authored Aug 23, 2004

This patch changes hose_list from a simple linked list to a
"list.h"-style list.  This is in preparation for the runtime
addition/removal of PCI Host Bridges.
Signed-off-by: John Rose <johnrose@austin.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

fae337c7

[PATCH] ppc64: fix enable_surveillance() for power5 · d613adcd

Nathan Fontenot authored Aug 23, 2004

On some platforms (notably power5) you can't enable surveillance
(firmware/service processor watchdog) from the kernel - you have to do
it in the firmware.

This patch changes enable_surveillance() to make the message that is
printed in this situation more informative.  Additionaly, the rtas_call
was changed to rtas_set_indicator so as to avoid having to handle
RTAS_BUSY returns.
Signed-off-by: Nathan Fontenot <nfont@austin.ibm.com>
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

d613adcd

Merge bk://ppc.bkbits.net/for-linus-ppc64 · bf851860
Linus Torvalds authored Aug 23, 2004
```
into ppc970.osdl.org:/home/torvalds/v2.6/linux
```
bf851860

Use F_SETLK instead of F_SETLK64 in nfs locking code. · 6a8e8a44

Linus Torvalds authored Aug 23, 2004

The code doesn't actually _care_ about 32/64-bit issues,
only about F_SETLK vs F_SETLKW, and the F_SETLK64 doesn't
exist except as a compatibility thing on 64-bit architectures
(since the regular one already _is_ 64-bit, of course).

6a8e8a44

Merge http://nfsclient.bkbits.net/linux-2.6 · 0646a4e4
Trond Myklebust authored Aug 23, 2004
```
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.6
```
0646a4e4
RPC,NFSv4: NFSv4 operations that create or destroy state on the · b4a558fd
Trond Myklebust authored Aug 23, 2004
```
   server are not allowed to be interrupted as that may result in the
   client and server disagreeing.
```
b4a558fd
NFSv4: Enable delegations by actually telling the server about our · fdd46e51
Trond Myklebust authored Aug 23, 2004
```
   recall ability.
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
fdd46e51
NFSv4: return all delegations we hold if the server issues a · ef7306b4
Trond Myklebust authored Aug 23, 2004
```
   NFS4ERR_CB_PATH_DOWN error.
```
ef7306b4
NFSv4: More aggressive caching if we have a delegation. · b42a8a16
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
b42a8a16
NFSv4: Delegated open. · 7129dfe5
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
7129dfe5
NFSv4: Recover delegations on server reboot. · 2ac2de8d
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
2ac2de8d
NFSv4: More delegation recall code · 0a3b5d3b
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
0a3b5d3b
NFSv4: Service delegation recall requests from the server. · 3f052fdc
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
3f052fdc
NFSv4: Further XDR cleanups in preparation for delegations. · f092be42
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
f092be42
NFSv4: XDR cleanups in preparation for delegations. · b6784786
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
b6784786
NFSv4: Add support for a delegation callback server. · 2fa8729d
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
2fa8729d
NFSv4: Basic code for managing delegation state. · 6d132c2f
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
6d132c2f
Merge fys.uio.no:/home/linux/bitkeeper/nfsclient-2.6 · 477d40b4
Trond Myklebust authored Aug 23, 2004
```
into fys.uio.no:/home/linux/bitkeeper/work/nfsclient-2.6
```
477d40b4
Merge http://nfsclient.bkbits.net/linux-2.6 · fec00732
Trond Myklebust authored Aug 23, 2004
```
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.6
```
fec00732

NFSv2/v3/v4: Make the rpc_ops->getattr method take a filehandle · 60fa4cfb

Trond Myklebust authored Aug 23, 2004

   rather than an inode argument. Fix up nfs_instantiate() and
   _nfs4_do_open to use this since doing a new lookup might be racy.

60fa4cfb

NFSv4: don't retry CREATE operations if the server returns · 26ee7f10
Trond Myklebust authored Aug 23, 2004
```
   NFS4ERR_DELAY on the GETATTR call.
```
26ee7f10
NFSv4: More cleanups of the NFSv4 state. · 90c1f6b2
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
90c1f6b2

NFSv2/v3/v4: Place NFS nfs_page shared data into a single structure · 6caf69fe

Trond Myklebust authored Aug 23, 2004

   that hangs off filp->private_data. As a side effect, this also
   cleans up the NFSv4 private file state info.
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

6caf69fe

NFSv4: Prime SETCLIENTID call for the delegation callback info. · af0ccd94
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
af0ccd94
NFSv4: On server reboot we need to recover byte-range locks. · ed373838
Trond Myklebust authored Aug 23, 2004
```
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
ed373838

NFSv4: Clean up the reboot recovery. Ensure that we exclude stateful · 191f7912

Trond Myklebust authored Aug 23, 2004

   operations by using a per-server read/write semaphore.
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

191f7912

NFSv4: Fix up the exception handling. Ensure we always handle · b6b42cec
Trond Myklebust authored Aug 23, 2004
```
   NFS4ERR_DELAY properly.
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>
```
b6b42cec
Merge http://nfsclient.bkbits.net/linux-2.6 · ecebe0fc
Trond Myklebust authored Aug 23, 2004
```
into fys.uio.no:/home/linux/bitkeeper/nfsclient-2.6
```
ecebe0fc

NFSv2: In the NFSv3 RFC, the sattr3 structure passed in the SETATTR · e143b1c8

Trond Myklebust authored Aug 23, 2004

   call allows for the client to request that the mtime and/or atime
   of an inode be set to the current server time, the given (client)
   time, or not changed.  The set-to-current-server value is used
   when you run "touch file" on the client.

The NFSv2 RFC defines no such encoding for the sattr structure. 
   However Solaris and Irix machine obey a convention where passing
   the invalid value mtime.useconds=1000000 means "set both mtime and
   atime to the current server time".  The convention is documented
   in the book "NFS Illustrated" by Brent Callaghan.  The patch below
   implements this convention for the Linux client and server (hence
   multiple To:s).
Signed-off-by: Greg Banks <gnb@sgi.com>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

e143b1c8

KCONFIG: In the kernel help for NFSv3 & NFSv4 client support both are · 9053c575

Trond Myklebust authored Aug 23, 2004

   listed as "the newer version ... of the NFS protocol". Obviously
   both can't be the newer version at the same time, so here's a
   patch to correct the text in such a way that only v4 is listed as
   the newer version. Patch is against 2.6.7-rc3 - please consider
   including it.
Signed-off-by: Jesper Juhl <juhl-lkml@dif.dk>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

9053c575

NFS: Now that file handle comparison ignores the unused parts of the · db9b4e94

Trond Myklebust authored Aug 23, 2004

   file handle container, there is no longer any need to clear the
   file handle container before copying in a file handle.  This
   allows us to remove a 128 byte memset() from several hot paths.
Signed-off-by: Chuck Lever <cel@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

db9b4e94

NFS: While the storage container for NFS file handles must be able to · 14671e6f

Trond Myklebust authored Aug 23, 2004

   store 128 bytes, usually NFS servers don't use file handles that
   are more than 32 bytes in size.  This patch creates an efficient
   mechanism for comparing file handles that ignores the unused bytes
   in a file handle.
Signed-off-by: Chuck Lever <cel@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

14671e6f

NFS: In 2.4, NFS O_DIRECT used the VFS's O_DIRECT logic to provide · 4ea5dc72

Trond Myklebust authored Aug 23, 2004

   direct I/O support for NFS files.  The 2.4 VFS O_DIRECT logic was
   block based, thus the NFS client had to provide a minimum
   allowable blocksize for O_DIRECT reads and writes on NFS files. 
   For various reasons we chose 512 bytes. In 2.6, there is no
   requirement for a minimum blocksize.  NFS O_DIRECT reads and
   writes can go to any byte at any offset in a file.  Thus we revert
   the blocksize setting for NFS file systems to the previous
   behavior, which was to advertise the "wsize" setting as the
   optimal I/O block size.  This improves the performance of
   applications like 'cp' which use this value as their transfer
   size.

This patch also exposes the server's reported disk block size in the
   f_frsize of the vfsstat structure.
Signed-off-by: Chuck Lever <cel@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

4ea5dc72

NFS: Clean up the logic that handles recovery from a failed mount · 7d4e31b1

Trond Myklebust authored Aug 23, 2004

   request. Get rid of nfs_put_super.
Signed-off-by: Chuck Lever <cel@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

7d4e31b1

NFS: Break the nfs_wreq_lock into per-mount locks. This helps prevent · 252470cd

Trond Myklebust authored Aug 23, 2004

   a heavy read and write workload on one mount point from
   interfering with workloads on other mount points.

Note that there is still some serialization due to the big kernel
   lock.
Signed-off-by: Chuck Lever <cel@netapp.com>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

252470cd

RPCSEC_GSS: Add the spkm3 common and client-side code. · 395f639e

Trond Myklebust authored Aug 23, 2004

Signed-off-by: Andy Adamson <andros@citi.umich.edu>
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

395f639e

RPCSEC_GSS: Missing newline in dprintk. · 1a7549b7

Trond Myklebust authored Aug 23, 2004

Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

1a7549b7

NFSv4: OK, so it's trivial and probably superfluous, but I don't see · 5220acb8

Trond Myklebust authored Aug 23, 2004

   why we shouldn't be slightly stricter here, so I'm just going to
   keep sending this until I'm told to stop.... Make sure that
   unmapped errors are approximately in the range of defined NFS4
   errors.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Signed-off-by: Trond Myklebust <trond.myklebust@fys.uio.no>

5220acb8