惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

A
About on SuperTechFans
人人都是产品经理
人人都是产品经理
量子位
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
博客园 - 三生石上(FineUI控件)
小众软件
小众软件
月光博客
月光博客
T
Tailwind CSS Blog
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
V
Visual Studio Blog
博客园 - 叶小钗
博客园 - 司徒正美
美团技术团队
博客园_首页
宝玉的分享
宝玉的分享
Apple Machine Learning Research
Apple Machine Learning Research
Hugging Face - Blog
Hugging Face - Blog
WordPress大学
WordPress大学
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
The Cloudflare Blog
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
有赞技术团队
有赞技术团队
D
DataBreaches.Net
Google DeepMind News
Google DeepMind News

LWN.net comments

tcmalloc's weird hack [LWN.net] Fixed? [LWN.net] mpd [LWN.net] Userspace AX.25 [LWN.net] RIP [LWN.net] My two cents... [LWN.net] pipx [LWN.net] Tragedy [LWN.net] A young man destined for glory [LWN.net] And 'less' won't let you search [LWN.net] A great loss [LWN.net] Sad and shocking news [LWN.net] Easy migration from Clementine [LWN.net] Sad coincidence [LWN.net] GNOME is actually usable thanks to Seth et al [LWN.net] Sad news :( [LWN.net] armhf supports preempt_rt [LWN.net] MusicBrainz accurracy [LWN.net] On open source maintainership [LWN.net] Let's stop here [LWN.net] Not a new thing [LWN.net] uv is indeed great pgmoneta Some comments on this on a Postgres blog feed [LWN.net] uv [LWN.net] going to Debian [LWN.net] Upgrading 64-bit-capable systems to 64-bit kernels? [LWN.net] Free Software foundations Maintainers can wait for code review but not for publish review? A reasonably extreme point of view [LWN.net]
My new developer experience with LLM [LWN.net]
mvollrath · 2026-06-16 · via LWN.net comments

My first patch was to stable leading up to 7.0.

I have an old PC that I still use for everything, and with RAM prices being what they were (and still are), felt like I should put some effort into maintaining that old hardware. I started with the ethernet driver, since it seemed like it should be pretty straightforward, and I'm generally interested in telemetry.

I started by pointing Claude at the main source file and asking it to find bugs. It found maybe 6 hits, and one of them turned out to be a very real bug. I spent a few days reading code and documentation to convince myself that it was indeed a very real bug.

With that new understanding of the patterns, next I wanted to be sure I could hack it without the LLM. I did code review on the same driver looking for any resources allocated in the driver probe which could be leaked on probe failure, and found one.

The next step was automating away that tedious code review, so I learned enough about coccinelle to scan all of the PCI ethernet drivers for the same probe leak, and it found another in a different driver.

I feel like the assistance with that first step was the real value of the LLM. It's kind of like having an expert to ask questions about any part of the kernel anytime you want, with the usual caveats of interacting with LLM for any purpose.

I do use the Assisted-by tag when the LLM was involved in finding the bug/change, iterating on the implementation, or reviewing the work. I can understand why a lot of people don't. There's no context about what parts of the work were done by the LLM, unless you add some noise to the commit description. If I'm feeling proud of myself for finding a bug or a big optimization myself, adding that label to the commit kind of steals the thunder. That's one reason I set out to make a few commits without any LLM assistance. Now I'm over it, and I'm just gonna do what works and follow the guidelines.

Maybe the guidelines can evolve to work around the psychology. For example, if it were acceptable to credit the LLM with different tags, that might help. On some commits I would credit it with Suggested-by, on others Reviewed-by, for implementation Co-authored-by, or Assisted-by as a shorthand for any or all of these. The normalization of anthropomorphism is a little creepy, but there's a reason we don't just use Assisted-by when a real person helps with a commit. The reduction cuts both ways.