Skip to content

deps: V8: backport dfcf1e86fac0 - #37245

Closed
targos wants to merge 1 commit into
nodejs:masterfrom
targos:v8-fix
Closed

deps: V8: backport dfcf1e86fac0#37245
targos wants to merge 1 commit into
nodejs:masterfrom
targos:v8-fix

Conversation

@targos

Copy link
Copy Markdown
Member

Original commit message:

[wasm] PostMessage of Memory.buffer should throw
PostMessage of an ArrayBuffer that is not detachable should result
in a DataCloneError.
Bug: chromium:1170176, chromium:961059
Change-Id: Ib89bbc10d2b58918067fd1a90365cad10a0db9ec
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2653810
Reviewed-by: Adam Klein <adamk@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#72415}

Refs: v8/v8@dfcf1e8

Original commit message:
[wasm] PostMessage of Memory.buffer should throw
PostMessage of an ArrayBuffer that is not detachable should result
in a DataCloneError.
Bug: chromium:1170176, chromium:961059
Change-Id: Ib89bbc10d2b58918067fd1a90365cad10a0db9ec
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2653810
Reviewed-by: Adam Klein <adamk@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#72415}
Refs: v8/v8@dfcf1e8
@targostargos added v8 engine Issues and PRs related to the V8 dependency. fast-track PRs that do not need to wait for 48 hours to land. labels Feb 6, 2021
@nodejs-github-botnodejs-github-bot added the build Issues and PRs related to build files or the CI. label Feb 6, 2021
@targos

Copy link
Copy Markdown
MemberAuthor

Fast-track to include in #37074.

@nodejs-github-bot

nodejs-github-bot commented Feb 6, 2021

Copy link
Copy Markdown
Collaborator

@aduh95aduh95 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

RSLGTM

@mcollinamcollina left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, and +1 to fast-track

@nodejs-github-bot

Copy link
Copy Markdown
Collaborator

@Trott

Trott commented Feb 6, 2021

Copy link
Copy Markdown
Member

Is the heap test failure in the initial V8 CI anything to worry about?

@targos

Copy link
Copy Markdown
MemberAuthor

Is the heap test failure in the initial V8 CI anything to worry about?

It's certainly not related to this change. I say we worry about it only if it happens again, maybe the machine was high on memory.

@targos

Copy link
Copy Markdown
MemberAuthor

Landed in aac2713

@targostargos closed this Feb 7, 2021
@targos
targos deleted the v8-fix branch February 7, 2021 09:25
targos added a commit that referenced this pull request Feb 7, 2021
Original commit message:
[wasm] PostMessage of Memory.buffer should throw
PostMessage of an ArrayBuffer that is not detachable should result
in a DataCloneError.
Bug: chromium:1170176, chromium:961059
Change-Id: Ib89bbc10d2b58918067fd1a90365cad10a0db9ec
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2653810
Reviewed-by: Adam Klein <adamk@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#72415}
Refs: v8/v8@dfcf1e8
PR-URL: #37245
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
BethGriggs pushed a commit that referenced this pull request Feb 8, 2021
Original commit message:
[wasm] PostMessage of Memory.buffer should throw
PostMessage of an ArrayBuffer that is not detachable should result
in a DataCloneError.
Bug: chromium:1170176, chromium:961059
Change-Id: Ib89bbc10d2b58918067fd1a90365cad10a0db9ec
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2653810
Reviewed-by: Adam Klein <adamk@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#72415}
Refs: v8/v8@dfcf1e8
PR-URL: #37245
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
BethGriggs added a commit that referenced this pull request Feb 8, 2021
Notable changes:
- **deps**:
- upgrade npm to 6.14.11 (Ruy Adorno)
(#37173)
- V8: backport dfcf1e86fac0 (Michaël Zasso)
(#37245)
- Note: Node.js is not believed to be vulnerable to CVE-2021-21148.
- **stream,zlib**: do not use \_stream\_\* anymore (Matteo Collina)
(#36618)
PR-URL: #37074
BethGriggs added a commit that referenced this pull request Feb 8, 2021
Notable changes:
- **deps**:
- upgrade npm to 6.14.11 (Ruy Adorno)
(#37173)
- V8: backport dfcf1e86fac0 (Michaël Zasso)
(#37245)
- Note: Node.js is not believed to be vulnerable to CVE-2021-21148.
- **stream,zlib**: do not use \_stream\_\* anymore (Matteo Collina)
(#36618)
PR-URL: #37074
@BethGriggsBethGriggs mentioned this pull request Feb 8, 2021
ruyadorno pushed a commit that referenced this pull request Feb 8, 2021
Original commit message:
[wasm] PostMessage of Memory.buffer should throw
PostMessage of an ArrayBuffer that is not detachable should result
in a DataCloneError.
Bug: chromium:1170176, chromium:961059
Change-Id: Ib89bbc10d2b58918067fd1a90365cad10a0db9ec
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2653810
Reviewed-by: Adam Klein <adamk@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#72415}
Refs: v8/v8@dfcf1e8
PR-URL: #37245
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
ruyadorno added a commit that referenced this pull request Feb 9, 2021
Notable changes:
* deps:
* V8: backport dfcf1e86fac0 (Michaël Zasso) [#37245](#37245)
* upgrade npm to 6.14.11 (Ruy Adorno) [#37173](#37173)
ruyadorno added a commit that referenced this pull request Feb 9, 2021
Notable changes:
* deps:
* V8: backport dfcf1e86fac0 (Michaël Zasso) [#37245](#37245)
* upgrade npm to 6.14.11 (Ruy Adorno) [#37173](#37173)
@ruyadornoruyadorno mentioned this pull request Feb 9, 2021
ruyadorno added a commit that referenced this pull request Feb 9, 2021
Notable changes:
* deps:
* upgrade npm to 6.14.11 (Ruy Adorno) [#37173](#37173)
* V8: backport dfcf1e86fac0 (Michaël Zasso) [#37245](#37245)
* Note: Node.js is not believed to be vulnerable to CVE-2021-21148.
PR-URL: #37286
BethGriggs added a commit that referenced this pull request Feb 9, 2021
Notable changes:
- **deps**:
- upgrade npm to 6.14.11 (Ruy Adorno)
(#37173)
- V8: backport dfcf1e86fac0 (Michaël Zasso)
(#37245)
- Note: Node.js is not believed to be vulnerable to CVE-2021-21148.
- **stream,zlib**: do not use \_stream\_\* anymore (Matteo Collina)
(#36618)
PR-URL: #37074
@ruyadorno

ruyadorno commented Feb 10, 2021

Copy link
Copy Markdown
Member

This did not landed cleanly in v12.x and I believe it might need to be properly backported.

I tried to land it directly and manually fixed conflicts (result being 680496e) but that ended up breaking all V8 ci tests. I believe a more informed backport is required here 😊

@targos

Copy link
Copy Markdown
MemberAuthor

If this patch doesn't work for v12.x, I don't know who has the knowledge and time to work on a correct one :(

danielleadams pushed a commit that referenced this pull request Feb 16, 2021
Original commit message:
[wasm] PostMessage of Memory.buffer should throw
PostMessage of an ArrayBuffer that is not detachable should result
in a DataCloneError.
Bug: chromium:1170176, chromium:961059
Change-Id: Ib89bbc10d2b58918067fd1a90365cad10a0db9ec
Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/2653810
Reviewed-by: Adam Klein <adamk@chromium.org>
Reviewed-by: Andreas Haas <ahaas@chromium.org>
Commit-Queue: Deepti Gandluri <gdeepti@chromium.org>
Cr-Commit-Position: refs/heads/master@{#72415}
Refs: v8/v8@dfcf1e8
PR-URL: #37245
Reviewed-By: Daniel Bevenius <daniel.bevenius@gmail.com>
Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com>
Reviewed-By: Rich Trott <rtrott@gmail.com>
Reviewed-By: Matteo Collina <matteo.collina@gmail.com>
Reviewed-By: Vladimir de Turckheim <vlad2t@hotmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
This was referenced Feb 16, 2021
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

buildIssues and PRs related to build files or the CI.fast-trackPRs that do not need to wait for 48 hours to land.v8 engineIssues and PRs related to the V8 dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants

@targos@nodejs-github-bot@Trott@ruyadorno@mcollina@danbev@cjihrig@vdeturckheim@aduh95