)]}'
{
  "commit": "f0ffab7e184b23ee798c96f3c96a6284a6824d75",
  "tree": "a22ed28845df4986e93b4243b7e16d60e943bc0e",
  "parents": [
    "b4d598e632d09a38d595bef0785e5c71656f8f96"
  ],
  "author": {
    "name": "Al Viro",
    "email": "viro@zeniv.linux.org.uk",
    "time": "Wed Jun 18 18:23:41 2025 -0400"
  },
  "committer": {
    "name": "Al Viro",
    "email": "viro@zeniv.linux.org.uk",
    "time": "Mon Jun 23 11:05:38 2025 -0400"
  },
  "message": "take freeing of emptied mnt_namespace to namespace_unlock()\n\nFreeing of a namespace must be delayed until after we\u0027d dealt with mount\nnotifications (in namespace_unlock()).  The reasons are not immediately\nobvious (they are buried in -\u003eprev_ns handling in mnt_notify()), and\nhaving that free_mnt_ns() explicitly called after namespace_unlock()\nis asking for trouble - it does feel like they should be OK to free\nas soon as they\u0027ve been emptied.\n\nMake the things more explicit by setting \u0027emptied_ns\u0027 under namespace_sem\nand having namespace_unlock() free the sucker as soon as it\u0027s safe to free.\n\nSigned-off-by: Al Viro \u003cviro@zeniv.linux.org.uk\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "4ea72ecd26212afdd5e9f096d1150d99f6318b17",
      "old_mode": 33188,
      "old_path": "fs/namespace.c",
      "new_id": "b8abac07b79450e019f8debe7b4befc788765933",
      "new_mode": 33188,
      "new_path": "fs/namespace.c"
    }
  ]
}