)]}'
{
  "commit": "42bbcb07bfd0871e316974b3be276b7198be4b2e",
  "tree": "a5b047fdbac49e77435de78b3554ddb61650c65c",
  "parents": [
    "6060ec8de0b0cbba99813d1ae97d8d5f201850e7"
  ],
  "author": {
    "name": "Luis Chamberlain",
    "email": "mcgrof@kernel.org",
    "time": "Mon Apr 28 15:34:47 2025 -0700"
  },
  "committer": {
    "name": "Luis Chamberlain",
    "email": "mcgrof@kernel.org",
    "time": "Mon Apr 28 15:34:47 2025 -0700"
  },
  "message": "nvme: add nvme_core.debug_large_atomics to force high awun as phys_bs\n\nA drive with atomic write support should have awun / nawun defined,\nfor these drives it should be possible to play with and experiment\nsafely with large atomics support up to awun / nawun settings if you are\ncompletely ignoring power failure situations. Add support to\nexperiment with this. The rationale to limit to awun / nawun is\nto avoid races with other on flight commands which otherwise\ncould cause unexpected results.\n\nThis also means this debug module parameter feature is not supported\nif your drive does not support atomics / awun / nawun. Use a taint\nflag in case this debug module parameter is used.\n\nExample usage: nvme_core.debug_large_atomics\u003d16384\n\nSuggested-by: Dan Helmick \u003cdan.helmick@samsung.com\u003e\nSigned-off-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e707fc42b9463d9ed4041c36ec1865b7cd7a94ab",
      "old_mode": 33188,
      "old_path": "drivers/nvme/host/core.c",
      "new_id": "26bfa51f2c0624b9312167b1f850a0dd2d1c5d94",
      "new_mode": 33188,
      "new_path": "drivers/nvme/host/core.c"
    }
  ]
}