diff options
| author | Jason Wang <jasowang@redhat.com> | 2012-05-17 13:25:43 +0800 |
|---|---|---|
| committer | Michael Roth <mdroth@linux.vnet.ibm.com> | 2012-06-29 10:22:30 -0500 |
| commit | b7093f294c330c4db789c077dac9d8611e4f8ee0 (patch) | |
| tree | 0a662b329a8944fe8017d340806fc4b1b57ab984 /cpu-exec.c | |
| parent | cd63a77e990f68a699ba220c8006386bd4379f81 (diff) | |
rtl8139: validate rx ring before receiving packets
Commit ff71f2e8cacefae99179993204172bc65e4303df prevent the possible
crash during initialization of linux driver by checking the operating
mode.This seems too strict as:
- the real card could still work in mode other than normal
- some buggy driver who does not set correct opmode after eeprom
access
So, considering rx ring address were reset to zero (which could be
safely trated as an address not intened to DMA to), in order to
both letting old guest work and preventing the unexpected DMA to
guest, we can forbid packet receiving when rx ring address is zero.
Tested-by: Avi Kivity <avi@redhat.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
(cherry picked from commit fcce6fd25f3e233f9da9ef01230a668ab35bd343)
Signed-off-by: Michael Roth <mdroth@linux.vnet.ibm.com>
Diffstat (limited to 'cpu-exec.c')
0 files changed, 0 insertions, 0 deletions