)]}'
{
  "commit": "c3fbaea340cff053c2eea0bfc695e6420df4da92",
  "tree": "d500728f48e8ca82dfa38ff8e21e094869ed5fc9",
  "parents": [
    "817852c5214fc8c44e75855776db8172a53b8157"
  ],
  "author": {
    "name": "Daeho Jeong",
    "email": "daehojeong@google.com",
    "time": "Tue Oct 13 15:30:06 2026 +0000"
  },
  "committer": {
    "name": "Jaegeuk Kim",
    "email": "jaegeuk@kernel.org",
    "time": "Tue Oct 13 17:38:58 2026 +0000"
  },
  "message": "fsck.f2fs: do not roll forward a checkpoint-disabled image\n\nWith checkpoint\u003ddisable, the kernel does not write a checkpoint at\numount. The last checkpoint is the one written when checkpoint was\ndisabled, with CP_DISABLED_FLAG set and without CP_UMOUNT_FLAG. The\nkernel never rolls forward such an image: f2fs_fill_super() skips the\nrecovery when CP_DISABLED_FLAG is set, and drops all writes after the\ncheckpoint.\n\nfsck decides to record fsync data only by CP_UMOUNT_FLAG, so it walks\nthe warm node chain of an image that the kernel will not recover. While\ncheckpoint is disabled, SSR reuses blocks written and invalidated after\nthe checkpoint, so the chain can point back to a block written earlier\nin the same session with the same cp_ver. fsck then reports \"detect\nlooped node chain\" and fails. xfstests generic/320 and generic/642 hit\nthis almost every time with checkpoint\u003ddisable.\n\nSkip recording fsync data when CP_DISABLED_FLAG is set, as the kernel\ndoes.\n\nSigned-off-by: Daeho Jeong \u003cdaehojeong@google.com\u003e\nSigned-off-by: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "8479ed11b428da121f5529aeaa16cb4562ad1036",
      "old_mode": 33188,
      "old_path": "fsck/mount.c",
      "new_id": "98d797ef7c8a17f1b973d2d2d075866277cabd27",
      "new_mode": 33188,
      "new_path": "fsck/mount.c"
    }
  ]
}