)]}'
{
  "commit": "7fc17e909edfb9bf421ee04e981d3d474175c7c7",
  "tree": "fdbe1700e6f5cf29b53901732e850f93ad04f87b",
  "parents": [
    "952fad8e323975c4e826b659087d2648777594a6"
  ],
  "author": {
    "name": "Jason Wang",
    "email": "jasowang@redhat.com",
    "time": "Wed Feb 14 22:17:34 2018 +0800"
  },
  "committer": {
    "name": "Daniel Borkmann",
    "email": "daniel@iogearbox.net",
    "time": "Wed Feb 14 15:34:27 2018 +0100"
  },
  "message": "bpf: cpumap: use GFP_KERNEL instead of GFP_ATOMIC in __cpu_map_entry_alloc()\n\nThere\u0027re several implications after commit 0bf7800f1799 (\"ptr_ring:\ntry vmalloc() when kmalloc() fails\") with the using of vmalloc() since\ncan\u0027t allow GFP_ATOMIC but mandate GFP_KERNEL. This will lead a WARN\nsince cpumap try to call with GFP_ATOMIC. Fortunately, entry\nallocation of cpumap can only be done through syscall path which means\nGFP_ATOMIC is not necessary, so fixing this by replacing GFP_ATOMIC\nwith GFP_KERNEL.\n\nReported-by: syzbot+1a240cdb1f4cc88819df@syzkaller.appspotmail.com\nFixes: 0bf7800f1799 (\"ptr_ring: try vmalloc() when kmalloc() fails\")\nCc: Michal Hocko \u003cmhocko@kernel.org\u003e\nCc: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\nCc: Matthew Wilcox \u003cwilly@infradead.org\u003e\nCc: Jesper Dangaard Brouer \u003cbrouer@redhat.com\u003e\nCc: akpm@linux-foundation.org\nCc: dhowells@redhat.com\nCc: hannes@cmpxchg.org\nSigned-off-by: Jason Wang \u003cjasowang@redhat.com\u003e\nAcked-by: Jesper Dangaard Brouer \u003cbrouer@redhat.com\u003e\nSigned-off-by: Daniel Borkmann \u003cdaniel@iogearbox.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "fbfdada6caeefa14b65e46e57f965c150a817fba",
      "old_mode": 33188,
      "old_path": "kernel/bpf/cpumap.c",
      "new_id": "a4bb0b34375a6c652f49d7719c1bd7e0e02c89e0",
      "new_mode": 33188,
      "new_path": "kernel/bpf/cpumap.c"
    }
  ]
}