今日重点:🗣️ 口语——AI 辅助写的补丁,视频会上被问「你自己懂多少」怎么接? 今天 linux-rt-devel 来了一封教科书级的自我披露:Mathieu Desnoyers(Efficios)的 [PATCH v2 00/21] sched/deadline: bandwidth accounting fixes and selftests。 他在封面第二段就直接说「这系列是 LLM 助手写的,我复核」——但没矮化自己,也没夸大工具。 拆他的五个说话动作:划边界、求精读、给对照、奔后果、曝工具短板。最后给你 30 秒现场演练。

🗣️ 现场:21 个补丁 + 一次开诚布公

/ section

背景:SCHED_DEADLINE 的带宽记账(root domain 的 total_bw 管准入,runqueue 的 this_bw 管本核余额) 在 CPU hotplug、亲和性变更、任务进出调度类这些边界上对不上账。Mathieu 的 21 补丁里 3 个能直接把内核干崩。但封面最抓人的不是 bug 列表,而是这句—— 他直接说这系列是在 LLM 助手协助下写成的,并坦承「症状消失不代表修法对」。 内核社区对 AI 参与的透明度讨论已久,这一封是罕见的、把尺度拿捏到位的第一人称样本。 下面五段引用全部逐字摘自真实邮件,来源附 lore 链接,点开可对照。

🗣️ 五个动作

/ section

① 开场一句话:交付什么 + 基于谁的工作。
原句:Hi Juri, / Please find in this series seventeen fixes to SCHED_DEADLINE bandwidth accounting, on top of your four in sched/urgent.
语境翻译:Juri 你好。这一系列是给 SCHED_DEADLINE 带宽记账的 17 个修复,基于你 sched/urgent 里那 4 个补丁。
要点:Hi + 名字,内核邮件里最稳的开场——既礼貌又不端着。Please find 是英式正式但内核社区高频, 约等于「附上/请查收」,比 here are 更沉稳。 on top of your four 一句话把「基线在哪、归功给谁」讲清楚,不收信人自己去猜。 开会第一句话照这个节奏:先报名字,再说「我交付什么」,最后一句「基于你 X」给足面子。
复述引导:合上原文,10 秒内说一句:Hi +维护者名,please find in this series N fixes to [子系统],on top of your [对方工作]。
来源:Mathieu Desnoyers,11-05 05:12 北京

② 划定能力边界:熟悉哪边、不熟悉哪边。
原句:I am at home with the concepts behind SCHED_DEADLINE, but not with its implementation, and these patches were written with an LLM assistant under my review ("How this was developed" below).
语境翻译:SCHED_DEADLINE 背后的概念我是熟的,但它的实现我不熟;这一系列补丁是在我复核之下由 LLM 助手写成的。
要点:at home with 是口语里「对……熟、玩得转」的地道说法,比 familiar with 更有「主人家」的味道。 关键在对照结构:at home with A but not with B——既不假装全懂,也不矮化成「我是外行」。 紧跟着 under my review 三个字把工具摆回助手位:它写、我审,主次一目了然。 在评审会上被追问「这些代码你懂多少」时,先划边界再讲流程,比含糊带过更立得住。
复述引导:用一句「I'm at home with [领域概念], but not with [具体实现], so these patches were written with [工具/助手] under my review」把边界划清楚——主从关系必须落在 under my review。
来源:Mathieu Desnoyers,11-05 05:12 北京

③ 求精读要指明对象:让「懂行的人」看「修复本身」。
原句:So I am asking those who know this code for a careful reading of the fixes themselves.
语境翻译:所以我想请懂这块代码的人,仔细审一遍修复本身。
要点:模糊请求是「请审一下」,Mathieu 给的是精准请求——those who know this code(圈定对象) + careful reading(深读不是浏览)+ the fixes themselves(不是 cover letter 也不是测试, 是修复本身)。三个修饰把「我到底要你干什么」钉死。 这个句式在开评审会时尤其有用:把请求从「你们随便看看」升级成「请 X 类人对 Y 部分做 Z 程度的审查」,对方接得住。
复述引导:说一句「I'm asking those who know [具体代码] for a careful reading of [具体产物]」——三个空一个都不许用 "this" 或 "it" 糊过去。
来源:Mathieu Desnoyers,11-05 05:12 北京

④ 区分「症状消失」和「修法正确」——评审里的金句结构。
原句:Most of them have a reproducer and were measured in VMs, which says that the symptom goes away, not that the fix is the one you would have written.
语境翻译:大多数都有 reproducer 也在 VM 里实测过——但这只能说明症状消失了,不代表修法就是你本会写的那一种。
要点:这句话值得抄下来背。which says that X, not that Y 结构把「验证能证明什么、不能证明什么」一刀切开。 the symptom goes away(症状消失)是底线,the fix is the one you would have written(这就是你会写的修法)是天花板——中间隔着的 就是维护者要审的东西。 会上被问「你测过了吗」时,别再只答「测了」;用 says that ..., not that ... 把「测到了什么」和「没测出什么」一次说清, 维护者立刻知道你不是只会跑 reproducer 的人。
复述引导:把「这个补丁我测过了」改写成「Each fix has a reproducer and was measured under [具体场景], which says that [底线结论], not that [天花板结论]」——空里必须出现具体场景。
来源:Mathieu Desnoyers,11-05 05:12 北京

⑤ 自曝工具短板:具体案例 + 怎么被纠正的。
原句:The assistant got things wrong on the way as well: one diagnosis of patch 11's bug was wrong twice over and was settled only by instrumenting a kernel; one assertion it had put in a test was itself racy and had to go;
语境翻译:这个助手一路上也出过错:补丁 11 的 bug 它两次诊断都错了,最后是靠给内核打桩才定的;它在测试里写的一个断言本身有竞态,不得不删掉。
要点:got things wrong on the way 比 made mistakes 更口语,on the way 暗示「在过程中、不是终点」。 wrong twice over 直译是「错了两遍」,地道说法就是「错了两次」。 settled only by 强调「只有靠 X 才解决」,把功劳归给正确的方法,不归给人。 had to go 三个字是「不得不删」的最地道表达——主语是那个有问题的断言,被动但干脆。 自曝短板不丢分,丢分的是含糊。给出具体案例 + 纠正方法,等于告诉维护者「我自己有纠错机制」。
复述引导:说一句「X got things wrong on the way as well: [一次具体误诊] was settled only by [纠正手段]; [一处具体错误] had to go」——案例必须带补丁号或文件级定位,不许只说「它有时不对」。
来源:Mathieu Desnoyers,11-05 05:12 北京

尾声:为什么这封重要。——内核社区对 AI 参与贡献还在立规矩,最敏感的就是「作者是不是真懂」。 Mathieu 没躲,也没用一行字带过:开篇就点名工具、划清边界、限定验证范围、自曝工具短板。这套动作组合起来, 既让维护者愿意花时间去审修复本身,也把自己从「AI 写代码的搬运工」救回到「懂场景、懂流程、对结果负责的工程师」。 下次被问「这补丁是谁写的」,照这五拍走一遍。

✨ 辅助彩蛋:四个能直接搬上会的词

/ section

★ 熟悉度、定位、崩溃、纠正——四个词各管一件事

都是真实原文里的用法,不是仿写

① at home with 对……熟悉、玩得转,如 I am at home with the concepts。 口语里「主人家在自己家里」的画面感,比 familiar with 更有自信。
② on top of 基于、在……之上,如 on top of your four in sched/urgent。 内核邮件里描述基线/前序补丁的固定词,开会接话也顺。
③ take the kernel down 把内核干崩,如 Three take the kernel down。 比 crash the kernel 更狠更口语,「拖垮」的画面感。
④ had to go 不得不删掉、留不得,如 one assertion ... was itself racy and had to go。 主语是「那个有问题的东西」,被动干脆,比 we removed it 更不动声色。
记忆钩子 at home with 说熟悉度,on top of 说基线,take down 说后果,had to go 说纠正。
溯源 四句全部出自 Mathieu 的封面(①②见开篇两段,③④见 bug 列表与开发经过两节)。

✍️ 今日练习

/ column
✍️ 场景:视频评审会上,维护者问「你这一系列补丁是 AI 写的,你自己到底掌握多少?」请在 30 秒内说完三句:第 1 句用 at home with A but not with B 划清你懂与不懂的边界;第 2 句说明验证方式,必须用 says that ..., not that ... 区分「症状消失」和「修法正确」;第 3 句主动给一个工具出错的具体案例 + 纠正手段。要求:不用 I think 或 sorry 开头;第 3 句必须出现 settled only by 或 had to go 中的一个。
💡 显示答案
参考作答(仿写示范,非原文):I'm at home with the workload these fixes serve, but not with every corner of the deadline scheduler, so the patches were written with an LLM assistant under my review. Each fix has a reproducer and was measured under CPU hotplug and cpuset moves, which says that the symptom goes away, not that the fix is the one you would have written. And to be straight: the assistant got things wrong on the way as well — one diagnosis of the underflow bug was wrong twice over and was settled only by instrumenting a kernel. 讲法要点:第 1 句把边界划在「workload 熟 / scheduler 实现不熟」,比直接说「我不懂」精确;第 2 句照抄原句的 says that ..., not that ... 对照,用 CPU hotplug and cpuset moves 把验证场景具体化;第 3 句 to be straight 是口语里「坦白说」的过渡,案例必须带 patch 级定位(the underflow bug)+ 纠正手段(instrumenting a kernel),不许只说「它有时不对」。
📖 原文:I am at home with the concepts behind SCHED_DEADLINE, but not with its implementation, and these patches were written with an LLM assistant under my review. So I am asking those who know this code for a careful reading of the fixes themselves. Most of them have a reproducer and were measured in VMs, which says that the symptom goes away, not that the fix is the one you would have written. ... The assistant got things wrong on the way as well: one diagnosis of patch 11's bug was wrong twice over and was settled only by instrumenting a kernel; one assertion it had put in a test was itself racy and had to go.
📎 原文引用

每日一句:Draw your line, name your reader, cap your claim.

仿写示范