RESOLVED FIXED Bug 200225
Possible use-after-move under NetworkConnectionToWebProcess::resourceLoadStatisticsUpdated()
https://bugs.webkit.org/show_bug.cgi?id=200225
Summary Possible use-after-move under NetworkConnectionToWebProcess::resourceLoadStat...
Chris Dumez
Reported 2019-07-29 08:24:57 PDT
Possible use-after-move under NetworkConnectionToWebProcess::resourceLoadStatisticsUpdated(). Was WTFMove()-ing the method parameter inside of a loop.
Attachments
Patch (2.50 KB, patch)
2019-07-29 08:27 PDT, Chris Dumez
no flags
Chris Dumez
Comment 1 2019-07-29 08:27:52 PDT
youenn fablet
Comment 2 2019-07-29 08:52:48 PDT
Comment on attachment 375076 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=375076&action=review > Source/WebKit/NetworkProcess/NetworkConnectionToWebProcess.cpp:699 > + auto* networkSession = networkProcess().networkSessionByConnection(connection()); This seems a bit strange. I hope we can remove networkSessionByConnection in the future since a process can have multiple pages with different sessions. It seems also strange that the statistics are not related to some sessionIDs. Would it not be safer to keep passing a copy of the statistics to all sessions? Or pass sessionID with the statistics?
Brent Fulgham
Comment 3 2019-07-29 09:07:38 PDT
Comment on attachment 375076 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=375076&action=review >> Source/WebKit/NetworkProcess/NetworkConnectionToWebProcess.cpp:699 >> + auto* networkSession = networkProcess().networkSessionByConnection(connection()); > > This seems a bit strange. > I hope we can remove networkSessionByConnection in the future since a process can have multiple pages with different sessions. > It seems also strange that the statistics are not related to some sessionIDs. > Would it not be safer to keep passing a copy of the statistics to all sessions? Or pass sessionID with the statistics? We should probably not pass the statistics to all sessions, as that could be viewed as a privacy violation if you were servicing multiple network clients (e.g. an Ephemeral session versus a default session versus a non-default session). We know that this can happen in use cases like Safari that may have multiple session to support different tasks unrelated to the main browsing session. We should be sending the sessionID with each of these messages. I started a patch doing this earlier this year but got sidetracked. I should revive it. I would support doing this in the short term to avoid the issue, and remove this use of 'networkSessionByConnection' with my proposed update later this cycle.
WebKit Commit Bot
Comment 4 2019-07-29 09:42:29 PDT
Comment on attachment 375076 [details] Patch Clearing flags on attachment: 375076 Committed r247905: <https://trac.webkit.org/changeset/247905>
WebKit Commit Bot
Comment 5 2019-07-29 09:42:31 PDT
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 6 2019-07-29 09:43:18 PDT
Note You need to log in before you can comment on or make changes to this bug.