)]}'
{
  "commit": "ad77dba64dc1a522014b2cd7376a67004140375b",
  "tree": "e1fd5a411c7bb76507456946395b90d730ebf81e",
  "parents": [
    "455ebeadf714f51e1dbbd6a022c74c9215b1cd76",
    "439f392084f8f7f59ab9d47a9579185accefe1d8"
  ],
  "author": {
    "name": "Jakub Kicinski",
    "email": "kuba@kernel.org",
    "time": "Tue Sep 15 17:58:36 2026 -0700"
  },
  "committer": {
    "name": "Jakub Kicinski",
    "email": "kuba@kernel.org",
    "time": "Tue Sep 15 17:58:37 2026 -0700"
  },
  "message": "Merge branch \u0027net-drop_monitor-fix-concurrency-issues-preemption-warning-and-buffer-overrun\u0027\n\nEric Dumazet says:\n\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\nnet: drop_monitor: fix concurrency issues, preemption warning, and buffer overrun\n\nThis series addresses several issues discovered in the drop_monitor subsystem:\n\nPatch 1 adds missing tracepoint unregistration synchronization to the\nnet_dm_trace_on_set() error unwind path, preventing in-flight probes\nfrom scheduling work after the module reference has been dropped.\n\nPatch 2 resolves a race condition during monitoring teardown where per-CPU\ntimers can be re-armed after deletion if a concurrent worker encounters a\nmemory allocation failure, switching to timer_shutdown_sync().\n\nPatch 3 fixes a CONFIG_DEBUG_PREEMPT warning reported by syzbot when\nkfree_skb() is invoked from preemptible process context, using raw_cpu_ptr()\nsince each per-CPU queue is safely protected by its own spinlock.\n\nPatch 4 fixes an out-of-bounds write in reset_per_cpu_data() where memset()\noverwrote the allocated SKB tailroom by sizeof(struct nlattr) bytes.\n\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\n\nLink: https://patch.msgid.link/20260910204612.3762015-1-edumazet@google.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n",
  "tree_diff": []
}