)]}'
{
  "commit": "24b57b3ec503e55c078589a968cfc9b1027e459d",
  "tree": "9384bd05062f8ec40f4ff9e1141ad5c9961dc3fd",
  "parents": [
    "0c648dfa1d9aad555542f2a423ea3d064652da49"
  ],
  "author": {
    "name": "Pratyush Yadav",
    "email": "ptyadav@amazon.de",
    "time": "Thu Mar 06 21:08:51 2025 +0000"
  },
  "committer": {
    "name": "Pratyush Yadav",
    "email": "ptyadav@amazon.de",
    "time": "Thu Mar 06 21:19:39 2025 +0000"
  },
  "message": "mm/memfd: allow preserving FD over FDBOX + KHO\n\nFor applications with a large amount of memory that takes time to\nrebuild, reboots to consume kernel upgrades can be very expensive. FDBox\nallows preserving file descriptors over kexec using KHO. Combining that\nwith memfd gives those applications reboot-persistent memory that they\ncan use to quickly save and reconstruct that state.\n\nWhile memfd is backed by either hugetlbfs or shmem, currently only\nsupport on shmem is added for this. Allow saving and restoring shmem FDs\nover FDBOX + KHO.\n\nThe memfd FDT node itself does not contain much information. It just\ncreates a subnode and passes it over to shmem to do its thing. Similar\nbehaviour is followed on the restore side.\n\nSince there are now two paths of getting a shmem file, refactor the file\nsetup into its own function called memfd_setup_file(). It sets up the\nfile flags, mode, etc., and sets fdbox ops if enabled.\n\nSigned-off-by: Pratyush Yadav \u003cptyadav@amazon.de\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "37f7be57c2f505cbee9c5d7b661dfd6c1e99b758",
      "old_mode": 33188,
      "old_path": "mm/memfd.c",
      "new_id": "1c32e66197f6d0843caf0cbad6c50e4609bb52e7",
      "new_mode": 33188,
      "new_path": "mm/memfd.c"
    }
  ]
}