)]}'
{
  "commit": "be6f0d0bae229ebd03e9bfe736f78e2d6b35885f",
  "tree": "4e05b3c36e18ca6d91a6e1ff006e264fda0bf7f8",
  "parents": [
    "89d8006259b81dd25c962f6cc8d7ab268d6ea426"
  ],
  "author": {
    "name": "T.J. Mercier",
    "email": "tjmercier@google.com",
    "time": "Wed Jul 22 13:54:42 2026 -0700"
  },
  "committer": {
    "name": "Jakub Kicinski",
    "email": "kuba@kernel.org",
    "time": "Fri Jul 24 14:53:16 2026 -0700"
  },
  "message": "selftests: drv-net: ncdevmem: Open /dev/udmabuf O_RDONLY\n\nWrite permissions on the /dev/udmabuf device file are not required to\nissue ioctls and allocate udmabufs. Applications should be opening this\nfile as O_RDONLY. The BPF dmabuf_iter selftest already does this. [1]\n\nUsers are pointing to these selftests as examples of how use udmabuf,\nand encountering permission errors on systems where write permissions\nare not available on /dev/udmabuf. Apply the principle of least\nprivilege to selftests which use udmabuf by removing the write access\nmode from drivers/net/hw/ncdevmem.c.\n\n[1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/tools/testing/selftests/bpf/prog_tests/dmabuf_iter.c?h\u003dv7.1#n49\n\nSigned-off-by: T.J. Mercier \u003ctjmercier@google.com\u003e\nReviewed-by: Bobby Eshleman \u003cbobbyeshleman@meta.com\u003e\nLink: https://patch.msgid.link/20260722205442.1894665-1-tjmercier@google.com\nSigned-off-by: Jakub Kicinski \u003ckuba@kernel.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d96e8a3b5a6526717135e8294c11e70010a310d7",
      "old_mode": 33188,
      "old_path": "tools/testing/selftests/drivers/net/hw/ncdevmem.c",
      "new_id": "ffe1d5c1fa4e1d30d7687458d1b6cd657b3fa5c4",
      "new_mode": 33188,
      "new_path": "tools/testing/selftests/drivers/net/hw/ncdevmem.c"
    }
  ]
}
