Dirty Pipe Explained

&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().

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>

I never knew that the standard command pipe is an “anonymous pipe”, but now “named pipes” make more sense.

I guess hardware RWX permissions on disks would be useful for this sort of thing.