Function Multiverses for Dynamic Variability

Rothberg, Valentin; Dietrich, Christian; Graf, Adam; Lohmann, Daniel

doi:10.1109/fas-w.2016.15

Cited by 1 publication

(7 citation statements)

References 15 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Similarly Rucjerbusch et al [39] have proposed a tool Gitar to enable runtime patching of applications in OSes running on IoT, M2M and resource-constrained devices. Table 2 shows that function-level runtime patching approaches are also adopted to perform dynamic variability in software system [33,38]. Most of these approaches are compiler assisted and implement function multiverse in the compiler to perform binary patching.…”

Section: Function-level Patchingmentioning

confidence: 99%

“…Vulnerable mobile applications Hotpaccher [36] Updating software Patch deployment Automated ELF binary application C-MultiVerse [38] Dynamic variability in system software Patch generation and deployment Automated Cloud system, legacy code base Gitar [39] Updating network stack of constrained devices Patch deployment Automated IoT, M2M, constrained devices' single Rime modules BinPatch [40] Patching Vulnerabilities in binary program (file level)…”

Section: Automatedmentioning

confidence: 99%

“…Flexibility, Robustness, Ease of Use, Effectiveness (low overhead) Kshot [3] X86 SMM, intel SGX ✓ ✓ --Effectiveness (low overhead), Trustworthiness Safestack [7] Linux ✓ -✓ ✓ Efficiency, Safely, Scalability Instaguard [8] Android ✓ -✓ ✓ Efficiency Replus [9] Linux ✓ -✓ ✓ Efficiency, Lightweight, DUSC [14] Java runtime system -✓ --Effectiveness (low overhead) Vulmet [15] Android --✓ -Correctness, Robustness, Efficiency Seamless [54] Linux -✓ ✓ -Effectiveness, Reliability Kup [23] Linux -✓ ✓ -Effectiveness, Reliability Cure [24] x86 -✓ ✓ -Effectiveness, Safety Piston [10] x86 ✓ --✓ Effectiveness, Persistence DynSec [28] x86 ✓ -✓ ✓ Correctness, Effectiveness (low overhead), Efficiency Gitar [39] Contiki, TinyOS ---✓ Efficiency, Sustainability, Maintainability HotAsap [29] Apache web server ✓ ---Correctness, Effectiveness (low overhead), Efficiency Karma [2] Android ✓ ---Adaptiveness, Safety, Effectiveness Multiverse [33] Linux, cPython, musl ✓ --✓ Efficiency, Ease of use, Flexibility, Portability C-Multiverse [38] Linux, cPython, musl ✓ --✓ Efficiency, Ease of use, Flexibility, Portability BinPatch [40] Linux, x86 ✓ ---Efficiency, Persistence ShawdowPatching [53] Virtual -✓ --Effectiveness Proteos [27] x86 Proteos ✓ ✓ ✓ -Effectiveness, Scalability, Reliability, Security Waitfree [43] x86, Linux --✓ ✓ Low overhead Vpatcher [13] Virtual ---✓ Correctness, Efficiency Orthus [12] Virtual -✓ --Efficiency, Effectiveness, Scalability HyperFresh [30] Virtual ✓ ✓ --Effectiveness, Low overhead ContainerECU [52] Electronic Control Unit (ECU) --✓ -Efficiency, Effectiveness (low overhead), Scalability Cetratus [11] x86, PowerPC ---✓ Stability MVEDSE [44] C program -✓ -✓ Availability, low latency, effectiveness Tedsuto [45] Java program -✓ ✓ -Effectiveness, Efficiency Kitsune [5,46] C-program -✓ ✓ -Effectiveness (no overhead), Efficiency Ginseng [47] C program -✓ ✓ -Scala...…”

Section: Memory Managementmentioning

confidence: 99%

“…In the case of long-living usage transactions (i.e., network sessions), the old entities may not be released for prolonged periods. Therefore, various dispatching mechanisms are implemented in conjunction with indirection layers to control which of the entities would be used at a given time [33,38]. Such dispatching mechanisms are the core of the co-exist & decay strategy, with the exact definitions of entity and dispatching algorithms used widely varying depending on the patching granularity supported.…”

Section: Safe Execution State Determinationmentioning

confidence: 99%

“…Such explicit versioning ensures compatibility between different copies of the co-existing code or data and external users. Due to the associated performance and memory overheads, multi-version dispatching may be used as a temporary measure while a developer is working on a longer-term solution [33,38]. In addition, to minimize at least the memory overhead, the gradual decay (i.e., cleanup) of old code and resource may be implemented as a feature of some patching solutions.…”

Section: Safe Execution State Determinationmentioning

confidence: 99%

See 4 more Smart Citations

Runtime Software Patching: Taxonomy, Survey and Future Directions

Islam¹,

Prokhorenko²,

Babar³

2022

Preprint

View full text Add to dashboard Cite

Runtime software patching aims to minimize or eliminate service downtime, user interruptions and potential data losses while deploying a patch. Due to modern software systems' high variance and heterogeneity, no universal solutions are available or proposed to deploy and execute patches at runtime. Existing runtime software patching solutions focus on specific cases, scenarios, programming languages and operating systems. This paper aims to identify, investigate and synthesize state-of-the-art runtime software patching approaches and gives an overview of currently unsolved challenges. It further provides insights on multiple aspects of runtime patching approaches such as patch scales, general strategies and responsibilities. This study identifies seven levels of granularity, two key strategies providing a conceptual model of three responsible entities and four capabilities of runtime patching solutions. Through the analysis of the existing literature, this research also reveals open issues hindering more comprehensive adoption of runtime patching in practice. Finally, it proposes several crucial future directions that require further attention from both researchers and practitioners.

show abstract

Section: Function-level Patchingmentioning

confidence: 99%