<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/net/sunrpc/auth.c, branch linux-2.6.34.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.34.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.34.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2010-04-22T19:35:55Z</updated>
<entry>
<title>SUNRPC: Fix a bug in rpcauth_prune_expired</title>
<updated>2010-04-22T19:35:55Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2010-04-22T19:35:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3d7b08945e54a3a5358d5890240619a013cb7388'/>
<id>urn:sha1:3d7b08945e54a3a5358d5890240619a013cb7388</id>
<content type='text'>
Don't want to evict a credential if cred-&gt;cr_expire == jiffies, since that
means that it was just placed on the cred_unused list. We therefore need to
use time_in_range() rather than time_in_range_open().

Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'nfs-for-2.6.33'</title>
<updated>2009-12-13T18:56:27Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2009-12-13T18:56:27Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=52c9948b1fd80381ba5a9a87dcc4fbe3cf4979b8'/>
<id>urn:sha1:52c9948b1fd80381ba5a9a87dcc4fbe3cf4979b8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>RPC: Fix two potential races in put_rpccred</title>
<updated>2009-12-03T13:10:17Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2009-12-03T13:10:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f0380f3d16df8f9e2fcd1d8c16fb0d94370bea99'/>
<id>urn:sha1:f0380f3d16df8f9e2fcd1d8c16fb0d94370bea99</id>
<content type='text'>
It is possible for rpcauth_destroy_credcache() to cause the rpc credentials
to be unhashed while put_rpccred is waiting for the rpc_credcache_lock on
another cpu. Should this happen, then we can end up calling
hlist_del_rcu(&amp;cred-&gt;cr_hash) a second time in put_rpccred, thus causing
list corruption.

Should the credential actually be hashed, it is also possible for
rpcauth_lookup_credcache to find and reference it before we get round to
unhashing it. In this case, the call to rpcauth_unhash_cred will fail, and
so we should just exit without destroying the cred.

Reported-by: Neil Brown &lt;neilb@suse.de&gt;
Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
</content>
</entry>
<entry>
<title>net: Move &amp;&amp; and || to end of previous line</title>
<updated>2009-11-30T00:55:45Z</updated>
<author>
<name>Joe Perches</name>
</author>
<published>2009-11-30T00:55:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f64f9e719261a87818dd192a3a2352e5b20fbd0f'/>
<id>urn:sha1:f64f9e719261a87818dd192a3a2352e5b20fbd0f</id>
<content type='text'>
Not including net/atm/

Compiled tested x86 allyesconfig only
Added a &gt; 80 column line or two, which I ignored.
Existing checkpatch plaints willfully, cheerfully ignored.

Signed-off-by: Joe Perches &lt;joe@perches.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Defer the auth_gss upcall when the RPC call is asynchronous</title>
<updated>2009-09-16T00:49:33Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2009-09-15T17:32:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5d351754fcf58d1a604aa7cf95c2805e8a098ad9'/>
<id>urn:sha1:5d351754fcf58d1a604aa7cf95c2805e8a098ad9</id>
<content type='text'>
Otherwise, the upcall is going to be synchronous, which may not be what the
caller wants...

Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
Signed-off-by: J. Bruce Fields &lt;bfields@citi.umich.edu&gt;
</content>
</entry>
<entry>
<title>Merge branch 'devel' into next</title>
<updated>2008-12-30T21:51:43Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2008-12-30T21:51:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=08cc36cbd1ee7d86422713bb21551eed1326b894'/>
<id>urn:sha1:08cc36cbd1ee7d86422713bb21551eed1326b894</id>
<content type='text'>
</content>
</entry>
<entry>
<title>optimize attribute timeouts for "noac" and "actimeo=0"</title>
<updated>2008-12-23T20:21:56Z</updated>
<author>
<name>Peter Staubach</name>
</author>
<published>2008-12-23T20:21:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=64672d55d93c26fb4035fd1a84a803cbc09cb058'/>
<id>urn:sha1:64672d55d93c26fb4035fd1a84a803cbc09cb058</id>
<content type='text'>
Hi.

I've been looking at a bugzilla which describes a problem where
a customer was advised to use either the "noac" or "actimeo=0"
mount options to solve a consistency problem that they were
seeing in the file attributes.  It turned out that this solution
did not work reliably for them because sometimes, the local
attribute cache was believed to be valid and not timed out.
(With an attribute cache timeout of 0, the cache should always
appear to be timed out.)

In looking at this situation, it appears to me that the problem
is that the attribute cache timeout code has an off-by-one
error in it.  It is assuming that the cache is valid in the
region, [read_cache_jiffies, read_cache_jiffies + attrtimeo].  The
cache should be considered valid only in the region,
[read_cache_jiffies, read_cache_jiffies + attrtimeo).  With this
change, the options, "noac" and "actimeo=0", work as originally
expected.

This problem was previously addressed by special casing the
attrtimeo == 0 case.  However, since the problem is only an off-
by-one error, the cleaner solution is address the off-by-one
error and thus, not require the special case.

    Thanx...

        ps

Signed-off-by: Peter Staubach &lt;staubach@redhat.com&gt;
Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
</content>
</entry>
<entry>
<title>SUNRPC: Remove the last remnant of the BKL...</title>
<updated>2008-12-23T20:21:31Z</updated>
<author>
<name>Trond Myklebust</name>
</author>
<published>2008-12-23T20:21:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=88a9fe8cae3bb52e82489447f45e8d7ba1409ca8'/>
<id>urn:sha1:88a9fe8cae3bb52e82489447f45e8d7ba1409ca8</id>
<content type='text'>
Somehow, this escaped the previous purge. There should be no need to keep
any extra locks in the XDR callbacks.

The NFS client XDR code only writes into private objects, whereas all reads
of shared objects are confined to fields that do not change, such as
filehandles...

Ditto for lockd, the NFSv2/v3 client mount code, and rpcbind.

The nfsd XDR code may require the BKL, but since it does a synchronous RPC
call from a thread that already holds the lock, that issue is moot.

Signed-off-by: Trond Myklebust &lt;Trond.Myklebust@netapp.com&gt;
</content>
</entry>
<entry>
<title>CRED: Wrap current-&gt;cred and a few other accessors</title>
<updated>2008-11-13T23:39:18Z</updated>
<author>
<name>David Howells</name>
</author>
<published>2008-11-13T23:39:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=86a264abe542cfececb4df129bc45a0338d8cdb9'/>
<id>urn:sha1:86a264abe542cfececb4df129bc45a0338d8cdb9</id>
<content type='text'>
Wrap current-&gt;cred and a few other accessors to hide their actual
implementation.

Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;
Acked-by: James Morris &lt;jmorris@namei.org&gt;
Acked-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
</content>
</entry>
<entry>
<title>CRED: Separate task security context from task_struct</title>
<updated>2008-11-13T23:39:16Z</updated>
<author>
<name>David Howells</name>
</author>
<published>2008-11-13T23:39:16Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b6dff3ec5e116e3af6f537d4caedcad6b9e5082a'/>
<id>urn:sha1:b6dff3ec5e116e3af6f537d4caedcad6b9e5082a</id>
<content type='text'>
Separate the task security context from task_struct.  At this point, the
security data is temporarily embedded in the task_struct with two pointers
pointing to it.

Note that the Alpha arch is altered as it refers to (E)UID and (E)GID in
entry.S via asm-offsets.

With comment fixes Signed-off-by: Marc Dionne &lt;marc.c.dionne@gmail.com&gt;

Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;
Acked-by: James Morris &lt;jmorris@namei.org&gt;
Acked-by: Serge Hallyn &lt;serue@us.ibm.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
</content>
</entry>
</feed>
