<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:media="http://search.yahoo.com/mrss/" version="2.0"><channel><title>云栖梦泽</title><link>https://www.iliuqi.com</link><atom:link href="https://www.iliuqi.com/rss.xml" rel="self" type="application/rss+xml"/><description>须知少时凌云志·曾许人间第一流</description><generator>Halo v2.24.2</generator><language>zh-cn</language><image><url>https://www.iliuqi.com/upload/logo.png</url><title>云栖梦泽</title><link>https://www.iliuqi.com</link></image><lastBuildDate>Tue, 16 Jun 2026 02:02:28 GMT</lastBuildDate><item><title><![CDATA[[Android稳定性] 第64篇 blk_mq_tags Use-After-Free 导致系统级 I/O 死锁]]></title><link>https://www.iliuqi.com/archives/android-stability-064</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5BAndroid%E7%A8%B3%E5%AE%9A%E6%80%A7%5D%20%E7%AC%AC64%E7%AF%87%20blk_mq_tags%20Use-After-Free%20%E5%AF%BC%E8%87%B4%E7%B3%BB%E7%BB%9F%E7%BA%A7%20I%2FO%20%E6%AD%BB%E9%94%81&amp;url=/archives/android-stability-064" width="1" height="1" alt="" style="opacity:0;">围绕 SPRD UMS9230 平台在 DDR Qualify.TT 测试中出现的冻屏问题，分析通过 ramdump、vmlinux 等工件定位到根因在内核 Block 层：blk_mq_tags 结构体发生 use-after-free，Scsi_Host.tag_set.tags 指针指向已被释放并被 cpumask/IRQ affinity 对象重用的 kmalloc-128 slab。内存中出现 “effective_affinity” 字符串，进一步印证该区域已被 IRQ 亲和性相关对象覆盖。由于 blk_mq_hw_ctx.tags 和 sched_tags 均为 NULL，当 E]]></description><guid isPermaLink="false">/archives/android-stability-064</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F06%2Fhalo_lze4foz.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="81804"/><category>与AI共生</category><category>Android稳定性</category><pubDate>Mon, 1 Jun 2026 09:44:33 GMT</pubDate></item><item><title><![CDATA[[Android稳定性] 第63篇 EROFS 解压缩页面 Use-After-Free 导致 Kernel Panic]]></title><link>https://www.iliuqi.com/archives/android-stability-063</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5BAndroid%E7%A8%B3%E5%AE%9A%E6%80%A7%5D%20%E7%AC%AC63%E7%AF%87%20EROFS%20%E8%A7%A3%E5%8E%8B%E7%BC%A9%E9%A1%B5%E9%9D%A2%20Use-After-Free%20%E5%AF%BC%E8%87%B4%20Kernel%20Panic&amp;url=/archives/android-stability-063" width="1" height="1" alt="" style="opacity:0;">围绕一次发生在 Qualcomm Ravelin SNP-AN00 平台上的 kernel panic，分析聚焦于 EROFS 压缩文件系统在 LZ4 解压过程中出现的 translation fault。根因是函数 z_erofs_lz4_decompress_partial 通过 __memcpy 访问压缩源页时，源页与目标页已被 page allocator 释放并填充为标准毒化值 dead000000000400，形成典型的 use-after-free。]]></description><guid isPermaLink="false">/archives/android-stability-063</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F06%2Fhalo_6ins1mb.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="84838"/><category>与AI共生</category><category>Android稳定性</category><pubDate>Mon, 1 Jun 2026 09:31:58 GMT</pubDate></item><item><title><![CDATA[[开源项目] GitNexus + Claude Code 配置与使用指南]]></title><link>https://www.iliuqi.com/archives/gitnexus-cookbook</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5B%E5%BC%80%E6%BA%90%E9%A1%B9%E7%9B%AE%5D%20GitNexus%20%2B%20Claude%20Code%20%E9%85%8D%E7%BD%AE%E4%B8%8E%E4%BD%BF%E7%94%A8%E6%8C%87%E5%8D%97&amp;url=/archives/gitnexus-cookbook" width="1" height="1" alt="" style="opacity:0;">GitNexus 是一款将代码仓库自动索引为知识图谱的工具，它会追踪项目中的每个依赖、调用链、集群和执行流，并通过 MCP（Model Context Protocol）暴露给 Claude Code，使 AI 代理真正理解代码的全局架构与复杂关系。在实际开发场景中，GitNexus 的核心价值体现在四个方面：让 AI 在分析和修改代码时不再遗漏隐含依赖和调用链；在改动代码前，可以准确评估变更的“爆炸半径”，降低引入潜在 bug 的风险；调试时能沿着调用链快速锁定错误源头，节省排查时间；进行重构和多文件重命名时更安全可控，减少对线上系统的影响。]]></description><guid isPermaLink="false">/archives/gitnexus-cookbook</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F05%2Fhalo_xeegyte.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="20892"/><category>开源项目推荐</category><pubDate>Wed, 6 May 2026 07:28:45 GMT</pubDate></item><item><title><![CDATA[[linux内存管理] 第046篇 Page Cache脏页回写机制深入分析]]></title><link>https://www.iliuqi.com/archives/linux-memory-management-046</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5Blinux%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86%5D%20%E7%AC%AC046%E7%AF%87%20Page%20Cache%E8%84%8F%E9%A1%B5%E5%9B%9E%E5%86%99%E6%9C%BA%E5%88%B6%E6%B7%B1%E5%85%A5%E5%88%86%E6%9E%90&amp;url=/archives/linux-memory-management-046" width="1" height="1" alt="" style="opacity:0;">围绕 Linux‑6.1 的 Page Cache 脏页回写机制展开，承接上一篇“脏页标记”，完整追踪数据从被修改到落盘的路径。先提炼回写要解决的三大问题：何时触发、由谁执行、如何高效写回；再从历史演进切入，对比早期全局 pdflush/kupdated 与现代按设备划分的 bdi_writeback 框架，重点解析 backing_dev_info、bdi_writeback 等核心结构中与脏页控制、阈值、速率限制和等待队列相关的关键字段。通过源码路径展示回写线程从 bdi_queue_work 被唤醒，到 wb_workfn 轮询任务、wb_do_writeout 扫描 inode 链表并]]></description><guid isPermaLink="false">/archives/linux-memory-management-046</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F04%2Fhalo_5aq6jjp.jpeg%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="37420"/><category>Linux内存管理</category><pubDate>Fri, 10 Apr 2026 09:09:20 GMT</pubDate></item><item><title><![CDATA[AI时代笔记工作流：构建下一代知识管理引擎]]></title><link>https://www.iliuqi.com/archives/my-ai-note</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=AI%E6%97%B6%E4%BB%A3%E7%AC%94%E8%AE%B0%E5%B7%A5%E4%BD%9C%E6%B5%81%EF%BC%9A%E6%9E%84%E5%BB%BA%E4%B8%8B%E4%B8%80%E4%BB%A3%E7%9F%A5%E8%AF%86%E7%AE%A1%E7%90%86%E5%BC%95%E6%93%8E&amp;url=/archives/my-ai-note" width="1" height="1" alt="" style="opacity:0;">]]></description><guid isPermaLink="false">/archives/my-ai-note</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F04%2Fhalo_rdvqhyg.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="109686"/><category>与AI共生</category><pubDate>Wed, 1 Apr 2026 03:07:02 GMT</pubDate></item><item><title><![CDATA[认知加速度：AI时代最残酷的鸿沟，正在此刻拉开]]></title><link>https://www.iliuqi.com/archives/flywheel</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%E8%AE%A4%E7%9F%A5%E5%8A%A0%E9%80%9F%E5%BA%A6%EF%BC%9AAI%E6%97%B6%E4%BB%A3%E6%9C%80%E6%AE%8B%E9%85%B7%E7%9A%84%E9%B8%BF%E6%B2%9F%EF%BC%8C%E6%AD%A3%E5%9C%A8%E6%AD%A4%E5%88%BB%E6%8B%89%E5%BC%80&amp;url=/archives/flywheel" width="1" height="1" alt="" style="opacity:0;">真正拉开的差距，不只是技术工具，而是思维范式的鸿沟。]]></description><guid isPermaLink="false">/archives/flywheel</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F03%2Fhalo_wfolmnt.jpeg%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="51038"/><category>与AI共生</category><pubDate>Tue, 24 Mar 2026 11:46:37 GMT</pubDate></item><item><title><![CDATA[Linux 内核崩溃分析报告 - AI]]></title><link>https://www.iliuqi.com/archives/linux-kernel-crash-ai-20260320</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=Linux%20%E5%86%85%E6%A0%B8%E5%B4%A9%E6%BA%83%E5%88%86%E6%9E%90%E6%8A%A5%E5%91%8A%20-%20AI&amp;url=/archives/linux-kernel-crash-ai-20260320" width="1" height="1" alt="" style="opacity:0;">作者展示了一份由 AI 生成的内核崩溃分析报告，并借此示范如何系统排查数组越界问题。案例中，qteeconnector@1 进程在 smcinvoke_dlkm 模块的 prepare_send_scm_msg() 内触发数据中止异常，原因是结构体中的边界字段被破坏：本应是一个很小的回调计数，却变成了 0x80010001 这种高得离谱的值，导致循环迭代数百万次，最终访问到未映射地址 0xffffff8005700000，引发崩溃。报告详细记录了从初始 bt、查看内核日志、确认模块基址，到对故障函数反汇编、检查结构体内存布局、用地址和寄存器值反证越界过程的完整推理链]]></description><guid isPermaLink="false">/archives/linux-kernel-crash-ai-20260320</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F03%2Fhalo_2lyrjnq.jpeg%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="51124"/><category>与AI共生</category><pubDate>Fri, 20 Mar 2026 10:24:57 GMT</pubDate></item><item><title><![CDATA[AI时代的思考：内核稳定性工程师离失业还有多久？]]></title><link>https://www.iliuqi.com/archives/will-ai-replace-me</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=AI%E6%97%B6%E4%BB%A3%E7%9A%84%E6%80%9D%E8%80%83%EF%BC%9A%E5%86%85%E6%A0%B8%E7%A8%B3%E5%AE%9A%E6%80%A7%E5%B7%A5%E7%A8%8B%E5%B8%88%E7%A6%BB%E5%A4%B1%E4%B8%9A%E8%BF%98%E6%9C%89%E5%A4%9A%E4%B9%85%EF%BC%9F&amp;url=/archives/will-ai-replace-me" width="1" height="1" alt="" style="opacity:0;">当 AI 能读 ramdump、调 crash、自己规划分析路径并输出报告时，内核稳定性工程师并不会被替代，但大量“敲命令、翻日志、整理报告”的重复劳动将被快速重构。作者提出的工具，不是简单封装 crash，而是让 AI 真正进入 ramdump 分析闭环：工程师只需提供标准化输入（vmcore 或分离 DDR dump 的 dump_spec、vmlinux、模块符号、crash 参数），AI 基于 Claude skills 和 MCP 调用 crash-mcp，在受控环境中打开会话、执行命令、解读输出、决定下一步分析动作，并最终按模板生成结构化报告。在这个时代，作为稳定性工程师，我们离失业还剩多久？]]></description><guid isPermaLink="false">/archives/will-ai-replace-me</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F03%2Fhalo_slxp98s.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="383228"/><category>与AI共生</category><pubDate>Wed, 11 Mar 2026 11:05:03 GMT</pubDate></item><item><title><![CDATA[[linux内存管理] 第045篇 per-CPU变量的静态与动态分配]]></title><link>https://www.iliuqi.com/archives/linux-memory-management-045</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5Blinux%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86%5D%20%E7%AC%AC045%E7%AF%87%20per-CPU%E5%8F%98%E9%87%8F%E7%9A%84%E9%9D%99%E6%80%81%E4%B8%8E%E5%8A%A8%E6%80%81%E5%88%86%E9%85%8D&amp;url=/archives/linux-memory-management-045" width="1" height="1" alt="" style="opacity:0;">延续前一篇对 per-CPU 基础与初始化的分析，这一部分聚焦于内核中的静态 per-CPU 变量及其使用方式。之后将问题的重点放在了动态per-CPU变量的分配逻辑上，并通过一个案例来分析分配逻辑的内部细节。]]></description><guid isPermaLink="false">/archives/linux-memory-management-045</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F03%2Fhalo_1s2bx7y.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="251940"/><category>Linux内存管理</category><pubDate>Fri, 6 Mar 2026 10:24:15 GMT</pubDate></item><item><title><![CDATA[[linux内存管理] 第044篇 per-CPU基础知识以及per-CPU分配器的初始化]]></title><link>https://www.iliuqi.com/archives/linux-memory-management-044</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5Blinux%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86%5D%20%E7%AC%AC044%E7%AF%87%20per-CPU%E5%9F%BA%E7%A1%80%E7%9F%A5%E8%AF%86%E4%BB%A5%E5%8F%8Aper-CPU%E5%88%86%E9%85%8D%E5%99%A8%E7%9A%84%E5%88%9D%E5%A7%8B%E5%8C%96&amp;url=/archives/linux-memory-management-044" width="1" height="1" alt="" style="opacity:0;">围绕 Linux 在 ARM64、SMP 场景下的并发挑战，本章聚焦内核 per‑CPU 变量机制及其底层内存布局。详细介绍了per-CPU的初始化流程，并以一个简单的案例来计算percpu memory的布局。]]></description><guid isPermaLink="false">/archives/linux-memory-management-044</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F03%2Fhalo_zmdvo6x.jpeg%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="32846"/><category>Linux内存管理</category><pubDate>Wed, 4 Mar 2026 11:12:19 GMT</pubDate></item><item><title><![CDATA[[Android稳定性] 第62篇 内核访问与tee共享的内存数据异常造成内存越界]]></title><link>https://www.iliuqi.com/archives/android-stability-062</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5BAndroid%E7%A8%B3%E5%AE%9A%E6%80%A7%5D%20%E7%AC%AC62%E7%AF%87%20%E5%86%85%E6%A0%B8%E8%AE%BF%E9%97%AE%E4%B8%8Etee%E5%85%B1%E4%BA%AB%E7%9A%84%E5%86%85%E5%AD%98%E6%95%B0%E6%8D%AE%E5%BC%82%E5%B8%B8%E9%80%A0%E6%88%90%E5%86%85%E5%AD%98%E8%B6%8A%E7%95%8C&amp;url=/archives/android-stability-062" width="1" height="1" alt="" style="opacity:0;">通过trace32分析寄存器信息，对着代码精准找到异常点，发现原来是内存越界的问题导致，并通过限制内存区域大小来屏蔽这个问题。]]></description><guid isPermaLink="false">/archives/android-stability-062</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F03%2Fhalo_mtt8fgo.jpeg%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="46802"/><category>Android稳定性</category><pubDate>Mon, 2 Mar 2026 03:12:36 GMT</pubDate></item><item><title><![CDATA[[LRDP2] 解析插件之logcat]]></title><link>https://www.iliuqi.com/archives/LRDP2-005</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5BLRDP2%5D%20%E8%A7%A3%E6%9E%90%E6%8F%92%E4%BB%B6%E4%B9%8Blogcat&amp;url=/archives/LRDP2-005" width="1" height="1" alt="" style="opacity:0;">通过logcat_v3和logcat_vma两套解析方案，工具能够应对大多数Android设备的内存布局变化，成功从ramdump中还原出logcat日志。整个过程涉及进程内存读取、数据结构逆向、多线程解析、日志去重等技术点，充分体现了ramdump parser工具的灵活性和强大功能。 本文重点剖析了logcat_v3的实现细节，从定位log buffer，到解析日志块，再到合并内核日志，每一步都力求清晰。希望读者能从中了解到Android logcat在内存中的存储方式，以及离线解析工具背后的工作原理。]]></description><guid isPermaLink="false">/archives/LRDP2-005</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_8bjhidf.jpeg%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="48526"/><category>LRDP2</category><pubDate>Sat, 28 Feb 2026 06:28:58 GMT</pubDate></item><item><title><![CDATA[[linux内存管理] 第043篇 page cache 脏页跟踪机制]]></title><link>https://www.iliuqi.com/archives/linux-memory-management-043</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5Blinux%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86%5D%20%E7%AC%AC043%E7%AF%87%20page%20cache%20%E8%84%8F%E9%A1%B5%E8%B7%9F%E8%B8%AA%E6%9C%BA%E5%88%B6&amp;url=/archives/linux-memory-management-043" width="1" height="1" alt="" style="opacity:0;">深入解析了Page Cache中脏页的跟踪机制。文章详细阐述了address_space结构体的作用，并对比了mmap映射与write系统调用两种场景下的脏页标记原理。内容涵盖缺页异常处理、页表项操作及回写流程，重点分析了ext4文件系统的具体实现，为理解内核数据持久化奠定了基础。]]></description><guid isPermaLink="false">/archives/linux-memory-management-043</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_70vif5u.webp&amp;size=m" type="image/jpeg" length="55174"/><category>Linux内存管理</category><pubDate>Thu, 26 Feb 2026 03:56:37 GMT</pubDate></item><item><title><![CDATA[向 Linux 内核社区提交 patch 实操要点]]></title><link>https://www.iliuqi.com/archives/Submit-patch-implementations-to-the-Linux-kernel-community</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%E5%90%91%20Linux%20%E5%86%85%E6%A0%B8%E7%A4%BE%E5%8C%BA%E6%8F%90%E4%BA%A4%20patch%20%E5%AE%9E%E6%93%8D%E8%A6%81%E7%82%B9&amp;url=/archives/Submit-patch-implementations-to-the-Linux-kernel-community" width="1" height="1" alt="" style="opacity:0;">详尽介绍了通过git send-email方式向Linux内核社区提交补丁的完整流程。内容涵盖git和git send-email的安装配置，SMTP邮件发送环境的设置，如何规范填写commit信息、生成和检查patch格式，以及标准化邮件回复方法。文章指出：基于next分支开发、严格遵循社区指南、养成bottom-posting习惯、合理使用收件人和抄送自动化配置，都是与上游高效沟通的关键。新手可从修复warning类小问题入手，逐步熟悉内核社区流程与规范。文末列举了寻找补丁切入点和提升英文交流技能的建议，强调实践积累对个人成长与社区认可的重要性。]]></description><guid isPermaLink="false">/archives/Submit-patch-implementations-to-the-Linux-kernel-community</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_dmxoosz.jpeg%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="30082"/><category>Linux内核</category><pubDate>Thu, 26 Feb 2026 01:40:15 GMT</pubDate></item><item><title><![CDATA[基于 QEMU 与 VSCode 的 Linux 内核调试环境搭建指南]]></title><link>https://www.iliuqi.com/archives/qemu-vscode-debug</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%E5%9F%BA%E4%BA%8E%20QEMU%20%E4%B8%8E%20VSCode%20%E7%9A%84%20Linux%20%E5%86%85%E6%A0%B8%E8%B0%83%E8%AF%95%E7%8E%AF%E5%A2%83%E6%90%AD%E5%BB%BA%E6%8C%87%E5%8D%97&amp;url=/archives/qemu-vscode-debug" width="1" height="1" alt="" style="opacity:0;">调试Linux内核曾是令人头痛的难关，传统方法依赖命令行log与GDB，效率低下且过程繁琐。现在，结合QEMU系统模拟与VSCode图形化调试，开发者可轻松搭建现代Linux内核调试环境：全程支持源码级断点、变量实时查看和调用栈分析，大幅提升定位问题的直观性和效率。文章详细梳理从WSL环境准备、内核和BusyBox源码获取与编译、根文件系统和虚拟硬盘制作，到VSCode与GDB的精确联调配置，逐步消除复杂性壁垒。全流程适配跨平台开发需求，并针对构建中遇到的实际问题给出解决思路。通过本文指引，开发者不仅能简化内核调试流程，还能享受可视化带来的高效与便捷，为深入探索系统底层保驾护航。]]></description><guid isPermaLink="false">/archives/qemu-vscode-debug</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_3sgihan.webp&amp;size=m" type="image/jpeg" length="208426"/><category>技术分享</category><pubDate>Fri, 6 Feb 2026 06:55:59 GMT</pubDate></item><item><title><![CDATA[「纵朝生暮死，亦当惊鸿」]]></title><link>https://www.iliuqi.com/archives/V20260206001</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%E3%80%8C%E7%BA%B5%E6%9C%9D%E7%94%9F%E6%9A%AE%E6%AD%BB%EF%BC%8C%E4%BA%A6%E5%BD%93%E6%83%8A%E9%B8%BF%E3%80%8D&amp;url=/archives/V20260206001" width="1" height="1" alt="" style="opacity:0;">这个抖音视频以富有哲理的方式探讨生命与人生意义。 视频先以蜉蝣的短暂生命切入，它仅存活一天却要完成生老病死、结婚生子等过程，引出“你的一天就是它的一生”的对比。接着通过蜉蝣与蚂蚱、蚂蚱与青蛙的互动，展现不同生命对时间认知的差异，进而引申到人类对“来生”的思考。 随后，视频核心观点逐渐展开：许多人忽视了“很多事不需要所谓意义”的真相，生命本是一段旅程，意义由自己赋予。鼓励人们吃想吃的饭、见想见的人、看喜欢的风景、做喜欢的事。 最后，视频指出人生短暂，拼搏一生带不走物质，执着一生留不下爱恨，因此我们应珍惜当下，把时间用于爱与享受，而非争吵、伤心和计较，强调“活在当下”的重要性。]]></description><guid isPermaLink="false">/archives/V20260206001</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_0c8qkwa.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="202302"/><category>视频分享</category><pubDate>Fri, 6 Feb 2026 01:40:40 GMT</pubDate></item><item><title><![CDATA[[linux内存管理] 第042篇 Linux内核Page Cache机制深入分析]]></title><link>https://www.iliuqi.com/archives/linux-memory-management-042</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5Blinux%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86%5D%20%E7%AC%AC042%E7%AF%87%20Linux%E5%86%85%E6%A0%B8Page%20Cache%E6%9C%BA%E5%88%B6%E6%B7%B1%E5%85%A5%E5%88%86%E6%9E%90&amp;url=/archives/linux-memory-management-042" width="1" height="1" alt="" style="opacity:0;">Page Cache作为Linux内核提升文件访问性能的核心机制，通过将磁盘数据缓存于内存，显著减少磁盘I/O次数。文章深度解析了Page Cache的架构及其关键数据结构，系统梳理address_space在文件和内存页间的桥梁作用。详细讲解address_space及page结构体的核心字段，阐明它们如何精准映射文件数据，实现高效的数据定位与状态管理，同时详细描述了读流程下的文件映射和内存映射的代码流程。]]></description><guid isPermaLink="false">/archives/linux-memory-management-042</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_e5et2ny.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="151414"/><category>Linux内存管理</category><pubDate>Wed, 4 Feb 2026 04:03:28 GMT</pubDate></item><item><title><![CDATA[[linux内存管理] 第041篇 缺页异常之 do_swap_page：从 swap entry 到完整 swap-in 全流程]]></title><link>https://www.iliuqi.com/archives/linux-memory-management-041</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5Blinux%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86%5D%20%E7%AC%AC041%E7%AF%87%20%E7%BC%BA%E9%A1%B5%E5%BC%82%E5%B8%B8%E4%B9%8B%20do_swap_page%EF%BC%9A%E4%BB%8E%20swap%20entry%20%E5%88%B0%E5%AE%8C%E6%95%B4%20swap-in%20%E5%85%A8%E6%B5%81%E7%A8%8B&amp;url=/archives/linux-memory-management-041" width="1" height="1" alt="" style="opacity:0;">深入剖析AArch64架构中Linux缺页异常的处理流程，本文聚焦do_swap_page函数的定位及其在缺页处理中的关键角色。通过梳理PTE的多种状态分支，明确do_swap_page仅在PTE为非present且编码为swap entry或特殊entry时介入，对swap entry的结构、swp_entry_t的编码机制进行深度解析，阐释type与offset的打包方式及其如何映射到实际swap区。文章还系统区分了swap cache与page cache的本质差异：page cache负责文件页面管理，swap cache则专为匿名页与swap slot建立高效缓存。]]></description><guid isPermaLink="false">/archives/linux-memory-management-041</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_k0hidr6.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="153020"/><category>Linux内存管理</category><pubDate>Tue, 3 Feb 2026 12:06:37 GMT</pubDate></item><item><title><![CDATA[[灵感风暴] GKI 升级不再靠人肉：Aegis 自动风险分级与测试建议生成]]></title><link>https://www.iliuqi.com/archives/inspire-storm-005</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5B%E7%81%B5%E6%84%9F%E9%A3%8E%E6%9A%B4%5D%20GKI%20%E5%8D%87%E7%BA%A7%E4%B8%8D%E5%86%8D%E9%9D%A0%E4%BA%BA%E8%82%89%EF%BC%9AAegis%20%E8%87%AA%E5%8A%A8%E9%A3%8E%E9%99%A9%E5%88%86%E7%BA%A7%E4%B8%8E%E6%B5%8B%E8%AF%95%E5%BB%BA%E8%AE%AE%E7%94%9F%E6%88%90&amp;url=/archives/inspire-storm-005" width="1" height="1" alt="" style="opacity:0;">Android GKI 升级带来大量碎片化 commits，人工分析压力巨大，Aegis（神盾）工具应运而生。它通过结构化 JSON 输出，将琐碎提交转化为可追踪的影响分析，智能识别变更模块、风险、核心问题并生成自动化测试优先级建议，显著提升升级评估与回归测试的精准性。最终产出 HTML 和 Markdown 报告，图表化展示高风险点与回归重点，报告可一键分享团队，有效缓解人力压力，实现升级分析自主可控。]]></description><guid isPermaLink="false">/archives/inspire-storm-005</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_yominfk.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="101166"/><category>灵感风暴</category><pubDate>Tue, 3 Feb 2026 02:12:52 GMT</pubDate></item><item><title><![CDATA[[linux内存管理] 第040篇 文件映射与匿名映射]]></title><link>https://www.iliuqi.com/archives/linux-memory-management-040</link><description><![CDATA[<img src="https://www.iliuqi.com/plugins/feed/assets/telemetry.gif?title=%5Blinux%E5%86%85%E5%AD%98%E7%AE%A1%E7%90%86%5D%20%E7%AC%AC040%E7%AF%87%20%E6%96%87%E4%BB%B6%E6%98%A0%E5%B0%84%E4%B8%8E%E5%8C%BF%E5%90%8D%E6%98%A0%E5%B0%84&amp;url=/archives/linux-memory-management-040" width="1" height="1" alt="" style="opacity:0;">围绕 Linux 内存管理，文章清晰解释了匿名页和文件页的本质区别。匿名页用于存储临时数据，不与磁盘文件关联，典型如进程的堆、栈及 MAP_ANONYMOUS 映射，生命周期受进程控制，内存紧张时可被换出至 swap。文件页则对应磁盘文件，是文件缓存和 page cache 的载体，源自磁盘数据，即使进程结束页面也可能保留，用于如 mmap 文件映射、文件读写缓冲、可执行代码段和共享库。文章通过 meminfo 和进程 maps 的实际输出，详细对比两类内存页的来源、生命周期、换出机制及典型场景，并以表格形式全面总结两者在内存管理中的关键特性。内容深入浅出，既便于理解，又具有实操价值。]]></description><guid isPermaLink="false">/archives/linux-memory-management-040</guid><dc:creator>林渡</dc:creator><enclosure url="https://www.iliuqi.com/apis/api.storage.halo.run/v1alpha1/thumbnails/-/via-uri?uri=https%3A%2F%2Fcdn.iliuqi.com%2F2026%2F02%2Fhalo_8cinflz.webp%3Fx-oss-process%3Dstyle%2Fwatermark&amp;size=m" type="image/jpeg" length="70962"/><category>Linux内存管理</category><pubDate>Mon, 2 Feb 2026 03:02:09 GMT</pubDate></item></channel></rss>