arXivDaily arXiv每日学术速递 周一至周五更新
arXiv周末暂无论文更新,休息一下吧,周末愉快~~
arXiv 2607.02748cs.OScs.PLcs.SE
收藏

表征和弥合eBPF验证器拒绝中的诊断差距

Characterizing and Bridging the Diagnostic Gap in eBPF Verifier Rejections

UC Santa Cruz(加州大学圣克鲁兹分校);eunomia-bpf;Virginia Tech(弗吉尼亚理工大学);Telecom Paris(巴黎电信学院);University of Washington(华盛顿大学);University of Connecticut(康涅狄格大学)

Yusheng Zheng, Zhengjie Ji, Weichen Tao, Xiangyu Gao, Jianchang Su, Wei Zhang, Andi Quinn, Dan Williams

AI总结:

研究eBPF验证器拒绝程序时的诊断差距,通过对235次拒绝进行实证研究量化问题。提出bpfix工具重建证明过程,构建75个LLM修复任务基准评估,发现定位证明丢失位置对修复关键,bpfix可提升修复成功率。

摘要:

eBPF允许开发者在Linux内核中运行自定义程序,由验证器证明程序安全。当验证器拒绝程序时,不明确的错误使修复具有挑战性。我们对235次重现的拒绝进行实证研究,提出bpfix工具,构建基准评估LLM修复能力,表明定位证明丢失位置对指导修复至关重要。

英文摘要:

eBPF lets developers run custom programs inside the Linux kernel, where a verifier proves each program safe. However, when the verifier rejects a program, the unclear error makes repair challenging: the error reports where verification stopped, not where the program lost the proof the verifier required. To quantify this gap, we conduct an empirical study of 235 reproduced rejections, showing that 47% of rejections return only EINVAL, one error string maps to as many as nine distinct root causes, and 10 of the 12 root causes are eBPF-specific. Repair thus requires both domain knowledge and locating where the proof was lost, yet existing tools only help developers read the error. We present bpfix, which reconstructs where the required proof was established and where it was lost from the verifier log, and prints a Rust-like diagnostic. To evaluate bpfix and the ability of LLMs to help repair, we construct a benchmark of 75 LLM repair tasks. Current models achieve 0-37% one-shot success with the raw log, and replacing the log with the bpfix localization improves repair by 11-21pp, suggesting that locating where the proof was lost is key to guiding repair. bpfix is available at https://github.com/eunomia-bpf/bpfix

机构、总结、中文摘要均由AI分析而来,可能存在错误,请以论文正文为准。

↑