This patch fixes a bug with the recently added printk-times feature.

In the case where a printk consists of only the log level (followed
subsequently by printks with more text for the same line), the printk-times
code doesn't correctly recognize the end of the string, and starts emitting
chars at the 0 byte at the end of the string.

The patch below fixes this problem.  It also adjusts the handling of
printed_len in the routine, which was affected by the printk-times feature.
Signed-off-by: Tim Bird <tim.bird@am.sony.com>
Acked-by: Tony Luck <tony.luck@intel.com>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

This patch adds AGP support for the U3 northbridge used in Apple G5
machines to drivers/char/agp/uninorth-agp.c.  This patch is based on
earlier work by Jerome Glisse.  With this patch, the driver works in
both ppc32 and ppc64 kernels.
Signed-off-by: Paul Mackerras <paulus@samba.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

Paul Mackerras points out that the pci_get_class() call will
properly put away the old PCI device. Blush.

There are other bogosities in drivers/char/agp/generic.c.  I can't
believe Dave ever tested that code with an AGP 3.0 device.  If you pass
in a mode that has the AGP 3.0 bit set, agp_v3_parse_one() will first
clear that bit (and print a message), and then complain because you
haven't got that bit set in the mode, with a message that the caller is
broken.  Furthermore, if the mode passed in has both the 4x and 8x bits
set, the new code will give you 4x where the old code would give you 8x
(which is what the caller wanted).

The patch below fixes this.  It will work in the 99.99% of cases where
we have one AGP bridge and one AGP video card.  We should eventually
cope with multiple AGP bridges, but doing the matching of bridges to
video cards is a hard problem because the video card is not necessarily
a child or sibling of the PCI device that we use for controlling the AGP
bridge.  I think we need to see an actual example of a system with
multiple AGP bridges first.

Oh, and by the way, I have 3D working relatively well on my G5 with a
64-bit kernel (and 32-bit X server and clients), which is why I care
about AGP 3.0 support.  :)
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

The previous revert needed some more work to make it actually work.

into ppc970.osdl.org:/home/torvalds/v2.6/linux

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 Some servers return an error if the READDIR call attempts to read the
 fileid of a mountpoint.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 We want to reuse the same code to recover the NFSv4 state after a server
 reboot, a network partition, or a failover situation.

 Add a structure to contain those operations will that depend on the recovery
 scenario under consideration.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 Fixes a potential Oops at mount time.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 If retrying the request is not an option, we should just set state->state
 and be done with it.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 Encode the AUTH flavour in the clientid, since AUTH_UNIX and AUTH_GSS
 credentials will always conflict.

 Then, strategy is to first retry after sleeping for a lease period. If
 the server then still refuses our clientid, assume we have a conflicting
 client, out there, and try bumping a "uniquifier" variable.

 Give up if we're signalled, or if we've gone through the entire range
 of uniquifiers...
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 
 Add a mechanism for the VFS layer to retry pathname resolution if a file
 system returns ESTALE at any point during the resolution process.  Pathname
 resolution is retried once from the first component, using all real lookup
 requests.

 This provides effective recovery for most cases where files or directories
 have been replaced by other remote file system clients.  It also provides
 a foundation to build a mechanism by which file system clients can fail
 over transparently to a replicated server.

 Test-plan:
 Combinations of rsync and "ls -l" on multiple clients.  No stale file handles
 should be after directory trees are replaced.  Standard performance tests;
 little or no loss of performance is expected.

 Created: Fri, 11 Feb 2005 16:46:19 -0500
Signed-off-by: Chuck Lever <cel@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 The RPC client now reports the maximum payload size supported by the chosen
 transport method.  This is something a little less than 64KB for RPC over
 UDP, and about 2GB - 1 for RPC over TCP.  The effective rsize and wsize
 values are not allowed to exceed the reported maximum RPC payload size.
Signed-off-by: Chuck Lever <cel@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Remove broken_suid mount option (retry RPC after dropping privileges
upon EACCES): no longer used and questionable w.r.t. security.
Signed-off-by: Frank van Maarseveen <frankvm@frankvm.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 This patch makes two needlessly global functions static.
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Adrian Bunk <bunk@stusta.de>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 So we can distinguish between ENOMEM and EACCES errors.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 Ensure that credentials that are referenced by an RPC task, but that
 have been booted out of the credcache may still be refreshed.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 gc_flavor is used only for looking up the security service, which is an
 integer value that never changes. Store the latter instead of the former.

 Fix up a couple of dodgy casts between gss_cred and rpc_cred. Replace them
 with the appropriate container_of().
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 - Document the format of the gssd downcalls
 - Separate out "uid" field from rest of GSS context data struct
   since it will not be needed for the keyring-based contexts.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 Most existing servers do not implement RPCSEC_GSS for either the lockd or
 statd daemons.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 This makes for an interesting situation in which programs compiled
 to use flock() and running on the server will not see the locks that
 are set by the clients. The clients will, however, see both POSIX and
 flock() locks set by other clients.

 It is the best you can do, given the limitations of the protocol.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 AUTH_UNIX credentials really only depend on the process uid/gid/groups
 information. In particular there is no dependency on any strict rpc_client
 specific information. Might as well share them all between all RPC clients.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 There is only one AUTH_NULL "credential".
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>

 This will make initialization of statically allocated caches simpler.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>