)]}'
{
  "commit": "d3406d8f35664e13905fab03c0c5f038d0a6e825",
  "tree": "e5ed542013531eaade91bdb36843a24de605ed10",
  "parents": [
    "f20b8f20da8d16a33e435992a3552b90a86334fe"
  ],
  "author": {
    "name": "Luis Chamberlain",
    "email": "mcgrof@kernel.org",
    "time": "Fri Aug 13 16:13:50 2021 -0700"
  },
  "committer": {
    "name": "Luis Chamberlain",
    "email": "mcgrof@kernel.org",
    "time": "Fri Oct 29 11:32:32 2021 -0700"
  },
  "message": "kernel/module: add documentation for try_module_get()\n\nThere is quite a bit of tribal knowledge around proper use of\ntry_module_get() and that it must be used only in a context which\ncan ensure the module won\u0027t be gone during the operation. Document\nthis little bit of tribal knowledge.\n\nI\u0027m extending this tribal knowledge with new developments which it\nseems some folks do not yet believe to be true: we can be sure a\nmodule will exist during the lifetime of a sysfs file operation.\nFor proof, refer to test_sysfs test #32:\n\n./tools/testing/selftests/sysfs/sysfs.sh -t 0032\n\nWithout this being true, the write would fail or worse,\na crash would happen, in this test. It does not.\n\nSigned-off-by: Luis Chamberlain \u003cmcgrof@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c9f1200b23121a4199ca9fad1d97ce0d6a6c84ad",
      "old_mode": 33188,
      "old_path": "include/linux/module.h",
      "new_id": "35c98e4196cbe94a96d7c660557bec5b4040b23e",
      "new_mode": 33188,
      "new_path": "include/linux/module.h"
    }
  ]
}