)]}'
{
  "commit": "06c8dfbfc0e17e21d7ecc48ba5e58ca9d7de5b10",
  "tree": "4d6892947fd9adc65330f4edfc744cc5285d6b92",
  "parents": [
    "c56edf7cade274dffa7bcb50b182ec8aa81b7481"
  ],
  "author": {
    "name": "Aurelien Aptel",
    "email": "aaptel@nvidia.com",
    "time": "Thu Oct 29 16:52:40 2026 +0100"
  },
  "committer": {
    "name": "Aurelien Aptel",
    "email": "aaptel@nvidia.com",
    "time": "Thu Oct 29 16:52:40 2026 +0100"
  },
  "message": "srp_daemon: run port services without PrivateNetwork\n\nSince kernel v7.3, commit e9153a267119 (\"RDMA/srp: Make the SRP sysfs\nclass net namespace aware\") tags the infiniband_srp sysfs class with\nthe net namespace of the underlying RDMA device. The\nsrp_daemon_port@.service unit runs srp_daemon with PrivateNetwork\u003dyes,\nso the daemon now sees an empty /sys/class/infiniband_srp/ inside its\nprivate network namespace and fails to log in to any target, endlessly\nlogging:\n\n  srp_daemon: unable to open /sys/class/infiniband_srp/srp-mlx5_0-1/add_target, maybe ib_srp is not loaded\n\neven though ib_srp is loaded and writing add_target from a root shell\nin the init netns works. This makes the SRP initiator unusable through\nthe standard systemd service on any v7.3+ kernel.\n\nsrp_daemon fundamentally needs to run in the net namespace of the RDMA\ndevice it manages, both for the umad device and now for the sysfs\nclass, so network namespace isolation is not applicable to this\nservice. Set PrivateNetwork\u003dno.\n\nVerified on Ubuntu 26.10 (kernel 7.3.0-9-generic) against an SCST\ntarget: with PrivateNetwork\u003dyes no login ever happens; with this change\nboth ports log in within seconds.\n\nSigned-off-by: Aurelien Aptel \u003caaptel@nvidia.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "3d5a11e86cab85afb112f41aaee4d9b7344c2ae1",
      "old_mode": 33188,
      "old_path": "srp_daemon/srp_daemon_port@.service.in",
      "new_id": "778959856bf61b156744a7801db97f45588d2ded",
      "new_mode": 33188,
      "new_path": "srp_daemon/srp_daemon_port@.service.in"
    }
  ]
}