TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Dirty Pipe Explained

78 点作者 gtzi大约 3 年前

4 条评论

max_k大约 3 年前
&gt; pipe flag “PIPE_BUF_FLAG_CAN_MERGE”, which signifies that the data buffer inside the pipe can be merged, i.e, this flag notifies the kernel that the changes which are written to the page cache pointed to by the pipe shall be written back to the file<p>That&#x27;s not what this flag does. No pipe flag can ever cause writing dirty pages back to disk, because pipes have by definition nothing to do with files.<p>The CAN_MERGE flag tells the kernel that the next write() to the pipe can append data to this pipe buffer until it&#x27;s full, instead of creating a new pipe buffer for every write().
kccqzy大约 3 年前
I stopped reading when it starts explaining what&#x27;s memory management.<p>In contrast I found the explanation written by the original author an engaging read: <a href="https:&#x2F;&#x2F;dirtypipe.cm4all.com&#x2F;" rel="nofollow">https:&#x2F;&#x2F;dirtypipe.cm4all.com&#x2F;</a>
评论 #30929106 未加载
评论 #30932397 未加载
评论 #30928976 未加载
cyberge99大约 3 年前
I never knew that the standard command pipe is an “anonymous pipe”, but now “named pipes” make more sense.
评论 #30929197 未加载
staticassertion大约 3 年前
I guess hardware RWX permissions on disks would be useful for this sort of thing.
评论 #30931783 未加载
评论 #30942195 未加载