[v8.x] deps: V8: cherry-pick 64-bit hash seed commits#23274
[v8.x] deps: V8: cherry-pick 64-bit hash seed commits#23274hashseed wants to merge 1 commit intonodejs:v8.x-stagingfrom
Conversation
6eb0c4c to
a2e924e
Compare
|
@hashseed, could you take a look at the conflicts and run CI/V8 CI please? Thanks |
1dbd688 to
71cea05
Compare
This comment has been minimized.
This comment has been minimized.
1 similar comment
|
I pushed a rebased version to my branch, but for some reason github is not picking up the change. |
|
Compilation fail in Debug - https://ci.nodejs.org/job/node-test-commit-linux-containered/8019/nodes=ubuntu1604_sharedlibs_debug_x64/ Maybe related test fails: |
|
The compilation fail might have always been there... We only recently started failing CI on debug build fail. |
|
That was likely a bad merge from @psmarshall when he merged all the CPU profiler goodness. I'll fix it as a driveby. |
This serves as mitigation for the so-called HashWick vulnerability.
Original commit messages:
commit d5686a74d56fbb6985b22663ddadd66eb7b91519
Author: Yang Guo <yangguo@chromium.org>
Date: Mon Jul 16 11:19:42 2018
Extend hash seed to 64 bits
R=bmeurer@chromium.org, ulan@chromium.org
Bug: chromium:680662
Change-Id: I5e1486ad2a42db2998d5485a0c4e711378678e6c
Reviewed-on: https://chromium-review.googlesource.com/1136034
Reviewed-by: Marja Hölttä <marja@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{nodejs#54460}
commit 3833fef57368c53c6170559ffa524c8c69f16ee5
Author: Yang Guo <yangguo@chromium.org>
Date: Thu Sep 20 11:43:13 2018
Refactor integer hashing function names
We now clearly differentiate between:
- unseeded hash for 32-bit integers
- unseeded hash for 64-bit integers
- seeded hash for 32-bit integers
- seeded hash for strings
R=bmeurer@chromium.org
Bug: chromium:680662
Change-Id: I7459958c4158ee3501c962943dff8f33258bb5ce
Reviewed-on: https://chromium-review.googlesource.com/1235973
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{nodejs#56068}
commit 95a979e02d7154e45b293261a6998c99d71fc238
Author: Yang Guo <yangguo@chromium.org>
Date: Thu Sep 20 14:34:48 2018
Call into C++ to compute seeded integer hash
R=bmeurer@chromium.org
Bug: chromium:680662
Change-Id: I8dace89d576dfcc5833fd539ce698a9ade1cb5a0
Reviewed-on: https://chromium-review.googlesource.com/1235928
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{nodejs#56091}
commit 2c2af0022d5feb9e525a00a76cb15db9f3e38dba
Author: Yang Guo <yangguo@chromium.org>
Date: Thu Sep 27 16:37:57 2018
Use 64-bit for seeded integer hashes
R=petermarshall@chromium.org
Bug: chromium:680662
Change-Id: If48d1043dbe1e1bb695ec890c23e103a6cacf2d4
Reviewed-on: https://chromium-review.googlesource.com/1244220
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{nodejs#56271}
Refs: nodejs#23259
71cea05 to
7aef2d4
Compare
|
I made a drive-by fix which replaces |
|
Is this good for merging yet? |
I think it's customary for a releaser to merge into version branches. |
|
Linux CI: https://ci.nodejs.org/job/node-test-commit-linux/22758/ [Passed] |
This serves as mitigation for the so-called HashWick vulnerability.
Original commit messages:
commit d5686a74d56fbb6985b22663ddadd66eb7b91519
Author: Yang Guo <yangguo@chromium.org>
Date: Mon Jul 16 11:19:42 2018
Extend hash seed to 64 bits
R=bmeurer@chromium.org, ulan@chromium.org
Bug: chromium:680662
Change-Id: I5e1486ad2a42db2998d5485a0c4e711378678e6c
Reviewed-on: https://chromium-review.googlesource.com/1136034
Reviewed-by: Marja Hölttä <marja@chromium.org>
Reviewed-by: Ulan Degenbaev <ulan@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Commit-Queue: Yang Guo <yangguo@chromium.org>
Cr-Commit-Position: refs/heads/master@{#54460}
commit 3833fef57368c53c6170559ffa524c8c69f16ee5
Author: Yang Guo <yangguo@chromium.org>
Date: Thu Sep 20 11:43:13 2018
Refactor integer hashing function names
We now clearly differentiate between:
- unseeded hash for 32-bit integers
- unseeded hash for 64-bit integers
- seeded hash for 32-bit integers
- seeded hash for strings
R=bmeurer@chromium.org
Bug: chromium:680662
Change-Id: I7459958c4158ee3501c962943dff8f33258bb5ce
Reviewed-on: https://chromium-review.googlesource.com/1235973
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56068}
commit 95a979e02d7154e45b293261a6998c99d71fc238
Author: Yang Guo <yangguo@chromium.org>
Date: Thu Sep 20 14:34:48 2018
Call into C++ to compute seeded integer hash
R=bmeurer@chromium.org
Bug: chromium:680662
Change-Id: I8dace89d576dfcc5833fd539ce698a9ade1cb5a0
Reviewed-on: https://chromium-review.googlesource.com/1235928
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Benedikt Meurer <bmeurer@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56091}
commit 2c2af0022d5feb9e525a00a76cb15db9f3e38dba
Author: Yang Guo <yangguo@chromium.org>
Date: Thu Sep 27 16:37:57 2018
Use 64-bit for seeded integer hashes
R=petermarshall@chromium.org
Bug: chromium:680662
Change-Id: If48d1043dbe1e1bb695ec890c23e103a6cacf2d4
Reviewed-on: https://chromium-review.googlesource.com/1244220
Commit-Queue: Yang Guo <yangguo@chromium.org>
Reviewed-by: Peter Marshall <petermarshall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#56271}
Refs: #23259
PR-URL: #23274
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
|
landed in 7ab253f |
Notable changes: * **assert**: - backport some assert commits (Ruben Bridgewater) [#23223](#23223) * **deps**: - V8: cherry-pick 64-bit hash seed commits (Yang Guo) [#23274](#23274) * **http**: - added aborted property to request (Robert Nagy) [#20094](#20094) * **http2**: - backport http2 changes from 10.x (Kelvin Jin) [#22850](#22850) PR-URL: #23974
Notable changes:
* **assert**:
- backport some assert commits (Ruben Bridgewater)
[#23223](#23223)
* **deps**:
- upgrade to libuv 1.23.2 (cjihrig)
[#23336](#23336)
- V8: cherry-pick 64-bit hash seed commits (Yang Guo)
[#23274](#23274)
* **http**:
- added aborted property to request (Robert Nagy)
[#20094](#20094)
* **http2**:
- graduate from experimental (James M Snell)
[#22466](#22466)
PR-URL: #23974
Notable changes:
* **assert**:
- backport some assert commits (Ruben Bridgewater)
[#23223](#23223)
* **deps**:
- upgrade to libuv 1.23.2 (cjihrig)
[#23336](#23336)
- V8: cherry-pick 64-bit hash seed commits (Yang Guo)
[#23274](#23274)
* **http**:
- added aborted property to request (Robert Nagy)
[#20094](#20094)
* **http2**:
- graduate from experimental (James M Snell)
[#22466](#22466)
PR-URL: #23974
Notable changes:
* **assert**:
- backport some assert commits (Ruben Bridgewater)
[nodejs#23223](nodejs#23223)
* **deps**:
- upgrade to libuv 1.23.2 (cjihrig)
[nodejs#23336](nodejs#23336)
- V8: cherry-pick 64-bit hash seed commits (Yang Guo)
[nodejs#23274](nodejs#23274)
* **http**:
- added aborted property to request (Robert Nagy)
[nodejs#20094](nodejs#20094)
* **http2**:
- graduate from experimental (James M Snell)
[nodejs#22466](nodejs#22466)
PR-URL: nodejs#23974
This serves as mitigation for the so-called HashWick vulnerability.
Original commit messages:
Refs: #23259
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes