)]}'
{
  "commit": "e9917a000fcc370408c8b7b83f2e85dba5fffbd4",
  "tree": "481bf9190677ed2b55e73625e535b86047fc5800",
  "parents": [
    "f1682e94a38b66ee2551f3a5e4b36259a561c411"
  ],
  "author": {
    "name": "Steve French",
    "email": "sfrench@us.ibm.com",
    "time": "Fri Mar 31 21:22:00 2006 +0000"
  },
  "committer": {
    "name": "Steve French",
    "email": "sfrench@us.ibm.com",
    "time": "Fri Mar 31 21:22:00 2006 +0000"
  },
  "message": "[CIFS] Incorrect signature sent on SMB Read\n\nFixes Samba bug 3621 and kernel.org bug 6147\n\nFor servers which require SMB/CIFS packet signing, we were sending the\nwrong signature (all zeros) on SMB Read request.  The new cifs routine\nto do signatures across an iovec was not complete - and SMB Read, unlike\nthe new SMBWrite2, did not fall back to the older routine (ie use\nSendReceive vs. the more efficient SendReceive2 ie used the older\ncifs_sign_smb vs. the disabled  cifs_sign_smb2) for calculating signatures.\n\nThis finishes up cifs_sign_smb2/cifs_calc_signature2 so that the callers\nof SendReceive2 can get SMB/CIFS packet signatures.\n\nNow that cifs_sign_smb2 is supported, we could start using it in\nthe write path but this smaller fix does not include the change\nto use SMBWrite2 when signatures are required (which when enabled\nwill make more Writes more efficient and alloc less memory).\nCurrently Write2 is only used when signatures are not\nrequired at the moment but after more testing we will enable\nthat as well).\n\nThanks to James Slepicka and Sam Flory for initial investigation.\n\nSigned-off-by: Steve French \u003csfrench@us.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "c2cbe0ed98b3e6b0467637236cece58f66dd131a",
      "old_mode": 33188,
      "old_path": "fs/cifs/cifsencrypt.c",
      "new_id": "e7d63737e65110c1be3fddb6f7974ab7a1f16c44",
      "new_mode": 33188,
      "new_path": "fs/cifs/cifsencrypt.c"
    }
  ]
}