)]}'
{
  "commit": "a76511f3a40ea69ee4f5cd86e735e1c8a84f0aa2",
  "tree": "611250ea7db431fa52086fe456ced887e44ef5c1",
  "parents": [
    "d6c4583ad4923533ddc9f5792ed3b66f3b9f9feb"
  ],
  "author": {
    "name": "Russ Cox",
    "email": "rsc@golang.org",
    "time": "Wed Dec 08 18:05:11 2021 -0500"
  },
  "committer": {
    "name": "Filippo Valsorda",
    "email": "filippo@golang.org",
    "time": "Thu Dec 09 13:36:16 2021 +0000"
  },
  "message": "syscall: fix ForkLock spurious close(0) on pipe failure\n\nPipe (and therefore forkLockPipe) does not make any guarantees\nabout the state of p after a failed Pipe(p). Avoid that assumption\nand the too-clever goto, so that we don\u0027t accidentally Close a real fd\nif the failed pipe leaves p[0] or p[1] set \u003e\u003d 0.\n\nFixes #50057\nFixes CVE-2021-44717\n\nChange-Id: Iff8e19a6efbba0c73cc8b13ecfae381c87600bb4\nReviewed-on: https://team-review.git.corp.google.com/c/golang/go-private/+/1291270\nReviewed-by: Ian Lance Taylor \u003ciant@google.com\u003e\nReviewed-on: https://go-review.googlesource.com/c/go/+/370576\nRun-TryBot: Filippo Valsorda \u003cfilippo@golang.org\u003e\nTrust: Russ Cox \u003crsc@golang.org\u003e\nReviewed-by: Alex Rakoczy \u003calex@golang.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "64eb5ed9f047a80c5c2414572484fec131892421",
      "old_mode": 33188,
      "old_path": "src/syscall/exec_unix.go",
      "new_id": "0e41959ffe54301ff0bec90a39ddb174b02f0079",
      "new_mode": 33188,
      "new_path": "src/syscall/exec_unix.go"
    }
  ]
}