<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Clone3 on Nalar</title>
    <link>https://nalar.dev/tags/clone3/</link>
    <description>Recent content in Clone3 on Nalar</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sat, 19 Sep 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://nalar.dev/tags/clone3/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>CLONE_INTO_CGROUP Places a Child in Its Target cgroup at Creation</title>
      <link>https://nalar.dev/clone-into-cgroup-places-child-in-target-cgroup-at-creation/</link>
      <pubDate>Sat, 19 Sep 2026 00:00:00 +0000</pubDate>
      <guid>https://nalar.dev/clone-into-cgroup-places-child-in-target-cgroup-at-creation/</guid>
      <description>&lt;h1 id=&#34;clone_into_cgroup-places-a-child-in-its-target-cgroup-at-creation&#34;&gt;CLONE_INTO_CGROUP Places a Child in Its Target cgroup at Creation&lt;/h1&gt;&#xA;&lt;p&gt;A process created in one cgroup and moved to another has a short but real interval in the original cgroup. During that interval, accounting, resource controls, and freezer state come from the initial placement rather than the destination. Linux provides &lt;code&gt;CLONE_INTO_CGROUP&lt;/code&gt; so &lt;code&gt;clone3()&lt;/code&gt; can place the child in a cgroup v2 target as part of process creation.&lt;/p&gt;&#xA;&lt;p&gt;This changes the placement boundary. Instead of creating a task and repairing its cgroup membership afterward, the caller identifies the destination before the child exists.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
