| commit | 0cbd6e52215427f13dadcde4e58bce455519bb03 | |
| author | Akihiko Odaki <akihiko.odaki@daynix.com> | |
| Thu, 23 Feb 2023 10:20:11 +0000 (23 19:20 +0900) | ||
| committer | Jason Wang <jasowang@redhat.com> | |
| Fri, 10 Mar 2023 07:35:38 +0000 (10 15:35 +0800) | ||
| tree | 72f1787c5b7818110bdc1fe90c35769d762a3b66 | treesnapshot (tar.gz zip) |
| parent | dd32b5ea7eeea367058ec8e0f9eb41de41a8d106 | commitdiff |
e1000e: Do not assert when MSI-X is disabled later
Assertions will fail if MSI-X gets disabled while a timer for MSI-X
interrupts is running so remove them to avoid abortions. Fortunately,
nothing bad happens even if the assertions won't trigger as
msix_notify(), called by timer handlers, does nothing when MSI-X is
disabled.
This bug was found by Alexander Bulekov when fuzzing igb, a new
device implementation derived from e1000e:
https://patchew.org/QEMU/20230129053316.1071513-1-alxndr@bu.edu/
The fixed test case is:
fuzz/crash_aea040166819193cf9fedb810c6d100221da721a
Fixes: 6f3fbe4ed0 ("net: Introduce e1000e device emulation")
Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
Assertions will fail if MSI-X gets disabled while a timer for MSI-X
interrupts is running so remove them to avoid abortions. Fortunately,
nothing bad happens even if the assertions won't trigger as
msix_notify(), called by timer handlers, does nothing when MSI-X is
disabled.
This bug was found by Alexander Bulekov when fuzzing igb, a new
device implementation derived from e1000e:
https://patchew.org/QEMU/20230129053316.1071513-1-alxndr@bu.edu/
The fixed test case is:
fuzz/crash_aea040166819193cf9fedb810c6d100221da721a
Fixes: 6f3fbe4ed0 ("net: Introduce e1000e device emulation")
Signed-off-by: Akihiko Odaki <akihiko.odaki@daynix.com>
Signed-off-by: Jason Wang <jasowang@redhat.com>
| hw/net/e1000e_core.c | diffblobblamehistory |