)]}'
{
  "commit": "817852c5214fc8c44e75855776db8172a53b8157",
  "tree": "dfcc54abe2fa372ba07c7f9ac0ab7ab04038eb0f",
  "parents": [
    "394b729aab9c35e44c7487945ba64a630343a1d0"
  ],
  "author": {
    "name": "Daeho Jeong",
    "email": "daehojeong@google.com",
    "time": "Thu Oct 01 18:07:58 2026 +0000"
  },
  "committer": {
    "name": "Jaegeuk Kim",
    "email": "jaegeuk@kernel.org",
    "time": "Tue Oct 13 17:33:35 2026 +0000"
  },
  "message": "fsck.f2fs: enable fix_on when CP_RESIZEFS_FLAG is set in auto-fix mode\n\nCommit 9a31cefa2966 (\"fsck.f2fs: allow fsck to fix issues with online\nresize due to SPO\") added logic in sanity_check_ckpt() to recalculate\nand fix user_block_count when CP_RESIZEFS_FLAG is set after a sudden\npower-off during online resize.\n\nHowever, sanity_check_ckpt() calls f2fs_should_proceed() and checks\nc.fix_on before repairing user_block_count, while f2fs_should_proceed()\ndid not check CP_RESIZEFS_FLAG when setting c.fix_on in auto_fix (-a) or\npreen (-p) mode. As a result, running \u0027fsck.f2fs -a\u0027 after an SPO during\nonline shrink leaves c.fix_on unset and fails to repair the checkpoint.\n\nCheck CP_RESIZEFS_FLAG in f2fs_should_proceed() so that auto-fix and\npreen modes properly enable c.fix_on and recover the filesystem.\n\nFixes: 9a31cefa2966 (\"fsck.f2fs: allow fsck to fix issues with online resize due to SPO\")\nSigned-off-by: Daeho Jeong \u003cdaehojeong@google.com\u003e\nReviewed-by: Chao Yu \u003cchao@kernel.org\u003e\nSigned-off-by: Jaegeuk Kim \u003cjaegeuk@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "2fd8e1cb1f5268898410b58e4f2c491aca5b5201",
      "old_mode": 33188,
      "old_path": "fsck/mount.c",
      "new_id": "8479ed11b428da121f5529aeaa16cb4562ad1036",
      "new_mode": 33188,
      "new_path": "fsck/mount.c"
    }
  ]
}