)]}'
{
  "commit": "efc3dbc37412c027e363736b4f4c74ee5e8ecffc",
  "tree": "958b635fa7f52456c19247e892a3d92d21a448a7",
  "parents": [
    "36a1211970193ce215de50ed1e4e1272bc814df1"
  ],
  "author": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Tue Jan 24 17:03:44 2012 -0500"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Tue Jan 24 17:03:44 2012 -0500"
  },
  "message": "rds: Make rds_sock_lock BH rather than IRQ safe.\n\nrds_sock_info() triggers locking warnings because we try to perform a\nlocal_bh_enable() (via sock_i_ino()) while hardware interrupts are\ndisabled (via taking rds_sock_lock).\n\nThere is no reason for rds_sock_lock to be a hardware IRQ disabling\nlock, none of these access paths run in hardware interrupt context.\n\nTherefore making it a BH disabling lock is safe and sufficient to\nfix this bug.\n\nReported-by: Kumar Sanghvi \u003ckumaras@chelsio.com\u003e\nReported-by: Josh Boyer \u003cjwboyer@gmail.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "bb6ad81b671d055b89fbe74287ed328a834aac03",
      "old_mode": 33188,
      "old_path": "net/rds/af_rds.c",
      "new_id": "424ff622ab5f8e77dc69c7b54b98bdaafa350329",
      "new_mode": 33188,
      "new_path": "net/rds/af_rds.c"
    }
  ]
}