Self-Stabilizing and Private Distributed Shared Atomic Memory in Seldomly Fair Message Passing Networks

TL;DR

This paper introduces a novel self-stabilizing, private, distributed shared memory algorithm for message-passing networks that tolerates malicious faults and transient system faults, ensuring data privacy and system recovery.

Contribution

It presents the first combined approach for privacy, self-stabilization, and fault-tolerance in emulating atomic shared memory over message-passing networks.

Findings

Ensures no information leakage during malicious server responses.

Recovers from arbitrary transient faults in asynchronous settings.

Uses bounded storage during asynchronous, unfair executions.

Abstract

We study the problem of privately emulating shared memory in message-passing networks. The system includes clients that store and retrieve replicated information on N servers, out of which e are malicious. When a client access a malicious server, the data field of that server response might be different than the value it originally stored. However, all other control variables in the server reply and protocol actions are according to the server algorithm. For the coded atomic storage (CAS) algorithms by Cadambe et al., we present an enhancement that ensures no information leakage and malicious fault-tolerance. We also consider recovery after the occurrence of transient faults that violate the assumptions according to which the system is to behave. After their last occurrence, transient faults leave the system in an arbitrary state (while the program code stays intact). We present a self-stabilizing algorithm, which recovers after the occurrence of transient faults. This addition to Cadambe et al. considers asynchronous settings as long as no transient faults occur. The recovery from transient faults that bring the system counters (close) to their maximal values may include the use of a global reset procedure, which requires the system run to be controlled by a fair scheduler. After the recovery period, the safety properties are provided for asynchronous system runs that are not necessarily controlled by fair schedulers. Since the recovery period is bounded and the occurrence of transient faults is extremely rare, we call this design criteria self-stabilization in the presence of seldom fairness. Our self-stabilizing algorithm uses a bounded storage during asynchronous executions (that are not necessarily fair). To the best of our knowledge, we are the first to address privacy and self-stabilization in the context of emulating atomic shared memory in networked systems.