)]}'
{
  "commit": "caba4cbbd27d755572730801ac34fe063fc40a32",
  "tree": "71a5b42a697bbc4828ca7d2694f9ee8b90bdaade",
  "parents": [
    "ef954844c7ace62f773f4f23e28d2d915adc419f"
  ],
  "author": {
    "name": "Waiman Long",
    "email": "longman@redhat.com",
    "time": "Mon Aug 14 09:52:13 2017 -0400"
  },
  "committer": {
    "name": "Thomas Gleixner",
    "email": "tglx@linutronix.de",
    "time": "Mon Aug 14 16:51:01 2017 +0200"
  },
  "message": "debugobjects: Make kmemleak ignore debug objects\n\nThe allocated debug objects are either on the free list or in the\nhashed bucket lists. So they won\u0027t get lost. However if both debug\nobjects and kmemleak are enabled and kmemleak scanning is done\nwhile some of the debug objects are transitioning from one list to\nthe others, false negative reporting of memory leaks may happen for\nthose objects. For example,\n\n[38687.275678] kmemleak: 12 new suspected memory leaks (see\n/sys/kernel/debug/kmemleak)\nunreferenced object 0xffff92e98aabeb68 (size 40):\n  comm \"ksmtuned\", pid 4344, jiffies 4298403600 (age 906.430s)\n  hex dump (first 32 bytes):\n    00 00 00 00 00 00 00 00 d0 bc db 92 e9 92 ff ff  ................\n    01 00 00 00 00 00 00 00 38 36 8a 61 e9 92 ff ff  ........86.a....\n  backtrace:\n    [\u003cffffffff8fa5378a\u003e] kmemleak_alloc+0x4a/0xa0\n    [\u003cffffffff8f47c019\u003e] kmem_cache_alloc+0xe9/0x320\n    [\u003cffffffff8f62ed96\u003e] __debug_object_init+0x3e6/0x400\n    [\u003cffffffff8f62ef01\u003e] debug_object_activate+0x131/0x210\n    [\u003cffffffff8f330d9f\u003e] __call_rcu+0x3f/0x400\n    [\u003cffffffff8f33117d\u003e] call_rcu_sched+0x1d/0x20\n    [\u003cffffffff8f4a183c\u003e] put_object+0x2c/0x40\n    [\u003cffffffff8f4a188c\u003e] __delete_object+0x3c/0x50\n    [\u003cffffffff8f4a18bd\u003e] delete_object_full+0x1d/0x20\n    [\u003cffffffff8fa535c2\u003e] kmemleak_free+0x32/0x80\n    [\u003cffffffff8f47af07\u003e] kmem_cache_free+0x77/0x350\n    [\u003cffffffff8f453912\u003e] unlink_anon_vmas+0x82/0x1e0\n    [\u003cffffffff8f440341\u003e] free_pgtables+0xa1/0x110\n    [\u003cffffffff8f44af91\u003e] exit_mmap+0xc1/0x170\n    [\u003cffffffff8f29db60\u003e] mmput+0x80/0x150\n    [\u003cffffffff8f2a7609\u003e] do_exit+0x2a9/0xd20\n\nThe references in the debug objects may also hide a real memory leak.\n\nAs there is no point in having kmemleak to track debug object\nallocations, kmemleak checking is now disabled for debug objects.\n\nSigned-off-by: Waiman Long \u003clongman@redhat.com\u003e\nSigned-off-by: Thomas Gleixner \u003ctglx@linutronix.de\u003e\nCc: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nLink: http://lkml.kernel.org/r/1502718733-8527-1-git-send-email-longman@redhat.com\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "052481fbe3633f64b420c5bbd6deea3be261e6a9",
      "old_mode": 33188,
      "old_path": "init/main.c",
      "new_id": "7ec20cf7b111360a837fa25af3ec20a830e901e3",
      "new_mode": 33188,
      "new_path": "init/main.c"
    },
    {
      "type": "modify",
      "old_id": "17afb043016133f880c3c64b696b5093f28dc52e",
      "old_mode": 33188,
      "old_path": "lib/debugobjects.c",
      "new_id": "2f5349c6e81ae01b0cca972570f3b7920aca246e",
      "new_mode": 33188,
      "new_path": "lib/debugobjects.c"
    }
  ]
}