Given the lack of details on the fix, upstream bug, my concern here is with a possible incomplete fix, and us having to rush another SRU right after, or perhaps even making things worse (if the fix is later changed again).
I checked the commits in trunk[1], and spotted this one there at [2], with the corresponding changeset at [3] which matches your patch, but the referenced bug or even svn rev are not public :/
That commit[3] is at least the last one on that file, so they didn't change it again, which is good.
Given the lack of details on the fix, upstream bug, my concern here is with a possible incomplete fix, and us having to rush another SRU right after, or perhaps even making things worse (if the fix is later changed again).
I checked the commits in trunk[1], and spotted this one there at [2], with the corresponding changeset at [3] which matches your patch, but the referenced bug or even svn rev are not public :/
That commit[3] is at least the last one on that file, so they didn't change it again, which is good.
1. https:/ /www.virtualbox .org/log/ vbox/trunk /www.virtualbox .org/browser/ vbox/trunk? rev=104355 /www.virtualbox .org/changeset/ 104355/ vbox
2. https:/
3. https:/