Changes between Version 1 and Version 2 of Ticket #21862, comment 4

Ticket #21862, comment 4

v1	v2
6	6	I believe you are mistakenly using the term 'red herring', as the issue here is the memcpy() warning(s) themselves.
7	7
8		If the kernel is generating a WARNING and stacktrace, there's a good chance Virtualbox code is doing something it shouldn't. The smaller, unlikely possibility would be that there's a bug in memcopy() triggering these warnings as false-positives.
	8	If the kernel is generating a WARNING and stacktrace, there's a good chance Virtualbox code is doing something it shouldn't. The smaller, less likely possibility would be that there's a bug in memcopy() triggering these warnings as false-positives.