history/net/sunrpc, branch masterLinux kernel history
https://git.shady.money/history/atom?h=master2005-03-28T11:42:22Z[PATCH] swsusp: Add missing refrigerator calls2005-03-28T11:42:22ZPavel Machekpavel@ucw.cz2005-03-28T11:42:22Zurn:sha1:ca0a9bc2cf3937968f1a4395b8e8711c150afe96
This adds few more places where it is possible freeze kernel threads.
From: Nigel Cunningham <ncunningham@cyclades.com>
Signed-off-by: Pavel Machek <pavel@suse.cz>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
[NET] Convert sk_zapped into SOCK_ZAPPED flag2005-03-16T00:50:36ZThomas Graftgraf@suug.ch2005-03-16T00:50:36Zurn:sha1:3ad701b91f476c14cd094ed0874b68fac0f16e5e
Signed-off-by: Thomas Graf <tgraf@suug.ch>
Signed-off-by: David S. Miller <davem@davemloft.net>
[PATCH] RPC: remove bogus atomic_dec in auth_null2005-03-12T01:13:28ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-12T01:13:28Zurn:sha1:30fa4fec25794bebf646cc268363abf5cc9f1c75
The atomic_dec in nul_destroy() is harmless, but can trigger an underflow
error if the atomic_dec_and_test() debugging is turned on.
Problem diagnosed by: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
NFS,RPC: RPC client now advertises maximum payload size2005-03-10T13:01:43ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-10T13:01:43Zurn:sha1:afdc754f2b8528423553d0ed443341685fd1ae09
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>
RPC: remove broken_suid mount option2005-03-10T13:01:26ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-10T13:01:26Zurn:sha1:388a910da2a61717581135118611340a086aadb5
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>
RPC: Clean up of rpcauth_lookupcred() and rpcauth_bindcred()2005-03-10T13:00:33ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-10T13:00:33Zurn:sha1:a2832a8fe12d528689ebdde7711b184bf8f315a0
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
RPC: make rpcauth_lookupcred() return error codes.2005-03-10T13:00:17ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-10T13:00:17Zurn:sha1:b62d37e62c22ba2ce98cbf03d39fcf8397aa0a90
So we can distinguish between ENOMEM and EACCES errors.
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
RPC: Initialize the GSS context upon RPC credential creation.2005-03-10T13:00:00ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-10T13:00:00Zurn:sha1:5a9e20efe0843a2c0ba85897a19da3af166ef0d0
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
RPC: Remove dependency of RPCSEC_GSS upcalls on the credential cache2005-03-10T12:59:44ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-10T12:59:44Zurn:sha1:4d08b43c00f3e9a51096e1c165529d6692f71098
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>
RPCSEC_GSS: Enable expiring of credentials2005-03-10T12:59:27ZTrond Myklebusttrond.myklebust@fys.uio.no2005-03-10T12:59:27Zurn:sha1:6180efbee86a45b0ff7a27125c95cd4608bce8be
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>