[PATCH]Fix rpcauth in 2.2.18pre (was Re: bug in rpc code)

> " " == Hai-Pao Fan <[EMAIL PROTECTED]> writes: > Problem: > A returned address from kmalloc() can be overwritten to a wrong > place in rpcauth_lookup_credcache() routine. Hi Alan, The following patch fixes the bug in 2.2.18pre. As reported in the 2.4.0 patch on l-k,

[PATCH] Fix hashing in 2.4.0 rpcauth code (was Re: bug in rpc code)

> " " == Hai-Pao Fan <[EMAIL PROTECTED]> writes: > Problem: > A returned address from kmalloc() can be overwritten to a wrong > place in rpcauth_lookup_credcache() routine. Ouch. This is a bug that's been with us since 2.1.x at least... Linus, the problem is in fact

[PATCH] Fix hashing in 2.4.0 rpcauth code (was Re: bug in rpc code)

" " == Hai-Pao Fan [EMAIL PROTECTED] writes: Problem: A returned address from kmalloc() can be overwritten to a wrong place in rpcauth_lookup_credcache() routine. Ouch. This is a bug that's been with us since 2.1.x at least... Linus, the problem is in fact twofold. 1)

[PATCH]Fix rpcauth in 2.2.18pre (was Re: bug in rpc code)

" " == Hai-Pao Fan [EMAIL PROTECTED] writes: Problem: A returned address from kmalloc() can be overwritten to a wrong place in rpcauth_lookup_credcache() routine. Hi Alan, The following patch fixes the bug in 2.2.18pre. As reported in the 2.4.0 patch on l-k, the problem

bug in rpc code

Problem: A returned address from kmalloc() can be overwritten to a wrong place in rpcauth_lookup_credcache() routine. rpcauth_lookup_credcache(struct rpc_auth *auth, int taskflags) { ... if (!cred) { cred = auth->au_ops->crcreate(taskflags); } if (cred)

bug in rpc code

Problem: A returned address from kmalloc() can be overwritten to a wrong place in rpcauth_lookup_credcache() routine. rpcauth_lookup_credcache(struct rpc_auth *auth, int taskflags) { ... if (!cred) { cred = auth-au_ops-crcreate(taskflags); } if (cred)