[19506] in Kerberos_V5_Development
Re: Lookaside mechanism in KDC -- shared between processes?
daemon@ATHENA.MIT.EDU (Greg Hudson)
Thu Nov 10 11:30:20 2016
To: Rick van Rein <rick@openfortress.nl>, "krbdev@mit.edu" <krbdev@mit.edu>
From: Greg Hudson <ghudson@mit.edu>
Message-ID: <77f702e1-1447-57d9-4430-c170135d66de@mit.edu>
Date: Thu, 10 Nov 2016 11:30:04 -0500
MIME-Version: 1.0
In-Reply-To: <58249A74.7080100@openfortress.nl>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: krbdev-bounces@mit.edu
On 11/10/2016 11:04 AM, Rick van Rein wrote:
> I found that the hash table is a static array, so it will be shared
> among processes, but the entries are simply allocated with calloc() and
> would therefore be specific to each process. So how can process A
> detect that dispatch.c is active for a given KDC-REQ packet if that
> packet is being dispatched from process B?
static arrays are not shared between processes. The KDC lookaside cache
is entirely specific to one process. It is intended as an optimization,
not as a guarantee that a request is only processed once.
(We have at times considered removing the lookaside cache, on the
grounds that its overhead may cost more than the optimization is worth
in typical scenarios. But so far we have not.)
_______________________________________________
krbdev mailing list krbdev@mit.edu
https://mailman.mit.edu/mailman/listinfo/krbdev
