Yong Yang
Research Subjects
Research Interests
Yong Yang has a total of 23 co-authors. Here are the top co-authors by number of shared publications:
- Tao Ma
Alibaba Group, Hangzhou, Zhejiang, China
3 shared publications - Teng Ma
Alibaba Group, Hangzhou, Zhejiang, China
2 shared publications - Chengqi Jiang
Shanghai Jiao Tong University
1 shared publication - Guangguan Wang
Alibaba Cloud, Hangzhou, Zhejiang, China
1 shared publication - Huanle Xu
University of Macau, Macau, Macao
1 shared publication - Jingxuan Li
Alibaba Cloud, Hangzhou, Zhejiang, China
1 shared publication
Latest Publications
- Open Access
- 5 November 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Architecture and Code Optimization
PLUGSCHED+: Efficient and General Live Update and Recovery for Linux Scheduler
The scheduler is a critical component of the operating system (OS) and is tightly coupled with Linux. Production-level clouds often host various workloads, and these workloads require different schedulers to achieve high performance. Furthermore, the scheduler may encounter faults during runtime, leading to the kernel panic. Thus the capability of updating and recovering the scheduler lively without rebooting the OS is crucial for the production environments. However, existing techniques only apply for the fine-grained function-level updates, or require extra constraints such as virtualization when performing update and recovery. We therefore propose Plugsched+ to enable scheduler live update and recovery with two key novelties. First, with the idea of modularization, Plugsched+ decouples the scheduler from the Linux kernel to be an independent module. Second, Plugsched+ uses the data rebuild technique to migrate the state from the old scheduler to the new one during live update, or clear anomalous data during live recovery. This scheme can be directly applied to the Linux kernel scheduler in production environments without replacing the kernel. Experimental and production results show that Plugsched+ can effectively update and recover the scheduler lively, and the downtime is no more than tens of milliseconds.
- 5 November 2026
- Published by Association for Computing Machinery (ACM) in ACM Transactions on Architecture and Code Optimization
Open AccessPLUGSCHED+: Efficient and General Live Update and Recovery for Linux Scheduler
The scheduler is a critical component of the operating system (OS) and is tightly coupled with Linux. Production-level clouds often host various workloads, and these workloads require different schedulers to achieve high performance. Furthermore, the scheduler may encounter faults during runtime, leading to the kernel panic. Thus the capability of updating and recovering the scheduler lively without rebooting the OS is crucial for the production environments. However, existing techniques only apply for the fine-grained function-level updates, or require extra constraints such as virtualization when performing update and recovery. We therefore propose Plugsched+ to enable scheduler live update and recovery with two key novelties. First, with the idea of modularization, Plugsched+ decouples the scheduler from the Linux kernel to be an independent module. Second, Plugsched+ uses the data rebuild technique to migrate the state from the old scheduler to the new one during live update, or clear anomalous data during live recovery. This scheme can be directly applied to the Linux kernel scheduler in production environments without replacing the kernel. Experimental and production results show that Plugsched+ can effectively update and recover the scheduler lively, and the downtime is no more than tens of milliseconds.
- Open Access
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 3792-3803
ABACI: Automated Downstream Bug Resolution via Semantic-Aware Bisection and Convergent Backporting
Downstream Linux kernel distributions, such as AnolisOS, continuously resolve defects inherited from the upstream codebase. This process requires two labor-intensive tasks: identifying the corresponding upstream fix patches, and adapting them for successful integration into downstream. Existing approaches address these tasks in isolation and suffer from fundamental limitations. Cross-version behavioral inconsistency makes it difficult to reliably verify defect existence and localize the correct fix patch across kernel versions. Besides, even when a fix patch is identified, unresolved prerequisite dependencies and structural divergence between upstream and downstream codebases render direct application infeasible. In this work, we present ABACI, an automated tool for resolving bugs discovered in downstream kernels. ABACI performs a four-phase fix patch localization process, employing semantic-aware bisection to correctly identify the target fix patch across kernel versions despite varying crash manifestations. Then ABACI performs convergent backporting, leveraging state-convergence-based dependency discovery to find prerequisite patches and collecting associated Fixes patches to form a self-consistent patch closure, followed by LLM-based adaptation to handle residual code-level conflicts. We evaluate ABACI on 26 real-world bugs from the Anolis community. ABACI achieves a fix patch localization success rate of 88.5% and a backporting success rate of 91.3%, ourperforming state-of-the-art works. Overall, ABACI has been deployed in the Anolis community, successfully resolving 21 real-world downstream kernel bugs and demonstrating its practical effectiveness.
- 7 October 2026
- Published by Association for Computing Machinery (ACM)
- p. 3792-3803
Open AccessABACI: Automated Downstream Bug Resolution via Semantic-Aware Bisection and Convergent Backporting
Downstream Linux kernel distributions, such as AnolisOS, continuously resolve defects inherited from the upstream codebase. This process requires two labor-intensive tasks: identifying the corresponding upstream fix patches, and adapting them for successful integration into downstream. Existing approaches address these tasks in isolation and suffer from fundamental limitations. Cross-version behavioral inconsistency makes it difficult to reliably verify defect existence and localize the correct fix patch across kernel versions. Besides, even when a fix patch is identified, unresolved prerequisite dependencies and structural divergence between upstream and downstream codebases render direct application infeasible. In this work, we present ABACI, an automated tool for resolving bugs discovered in downstream kernels. ABACI performs a four-phase fix patch localization process, employing semantic-aware bisection to correctly identify the target fix patch across kernel versions despite varying crash manifestations. Then ABACI performs convergent backporting, leveraging state-convergence-based dependency discovery to find prerequisite patches and collecting associated Fixes patches to form a self-consistent patch closure, followed by LLM-based adaptation to handle residual code-level conflicts. We evaluate ABACI on 26 real-world bugs from the Anolis community. ABACI achieves a fix patch localization success rate of 88.5% and a backporting success rate of 91.3%, ourperforming state-of-the-art works. Overall, ABACI has been deployed in the Anolis community, successfully resolving 21 real-world downstream kernel bugs and demonstrating its practical effectiveness.
- Open Access
- 11 August 2026
- Published by Association for Computing Machinery (ACM)
- p. 1752-1763
Rethinking Transparent TCP Replacement: Practical Lessons from SMC-R in the Cloud
Transparent TCP acceleration has been a subject of extensive academic research for years, aiming to bypass kernel overhead without modifying legacy applications. Prior work, however, largely emphasizes performance under idealized settings and provides limited discussion of how costs and gains manifest in real production environments. Over the past four years, we have deployed and evaluated SMC-R within Alibaba Cloud to accelerate general cloud workloads. Our experience reveals that transparent TCP replacement is far from "drop-in" in practice. The integration barriers and disruptions to the existing ecosystem incur substantial hidden costs. Furthermore, in many real-world scenarios, the Linux TCP stack is not the dominant performance bottleneck; instead, suboptimal application-layer behaviors and system configurations often exert a more decisive influence on end-to-end gains. These engineering realities explain why transparent TCP replacement remains active in academia but sees limited adoption in production. This paper systematically summarizes the fundamental hurdles we encountered and traces them to their root causes, aiming to provide the community with a more grounded perspective on the costs and benefits of transparent acceleration.
- 11 August 2026
- Published by Association for Computing Machinery (ACM)
- p. 1752-1763
Open AccessRethinking Transparent TCP Replacement: Practical Lessons from SMC-R in the Cloud
Transparent TCP acceleration has been a subject of extensive academic research for years, aiming to bypass kernel overhead without modifying legacy applications. Prior work, however, largely emphasizes performance under idealized settings and provides limited discussion of how costs and gains manifest in real production environments. Over the past four years, we have deployed and evaluated SMC-R within Alibaba Cloud to accelerate general cloud workloads. Our experience reveals that transparent TCP replacement is far from "drop-in" in practice. The integration barriers and disruptions to the existing ecosystem incur substantial hidden costs. Furthermore, in many real-world scenarios, the Linux TCP stack is not the dominant performance bottleneck; instead, suboptimal application-layer behaviors and system configurations often exert a more decisive influence on end-to-end gains. These engineering realities explain why transparent TCP replacement remains active in academia but sees limited adoption in production. This paper systematically summarizes the fundamental hurdles we encountered and traces them to their root causes, aiming to provide the community with a more grounded perspective on the costs and benefits of transparent acceleration.