diff options
| author | Jason Wang <jasowang@redhat.com> | 2022-06-22 09:29:40 +0800 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2022-06-24 02:49:48 -0400 |
| commit | c346dae4f3fbce51bbd4f2ec5e8c6f9b91e93163 (patch) | |
| tree | 4e3a09595a5ec554cf002679c587049c627fba49 /drivers/net/caif/caif_virtio.c | |
| parent | 03d9571706942fa653a4975709820596d13563c7 (diff) | |
| download | linux-stable-c346dae4f3fbce51bbd4f2ec5e8c6f9b91e93163.tar.gz linux-stable-c346dae4f3fbce51bbd4f2ec5e8c6f9b91e93163.tar.bz2 linux-stable-c346dae4f3fbce51bbd4f2ec5e8c6f9b91e93163.zip | |
virtio: disable notification hardening by default
We try to harden virtio device notifications in 8b4ec69d7e09 ("virtio:
harden vring IRQ"). It works with the assumption that the driver or
core can properly call virtio_device_ready() at the right
place. Unfortunately, this seems to be not true and uncover various
bugs of the existing drivers, mainly the issue of using
virtio_device_ready() incorrectly.
So let's add a Kconfig option and disable it by default. It gives
us time to fix the drivers and then we can consider re-enabling it.
Signed-off-by: Jason Wang <jasowang@redhat.com>
Message-Id: <20220622012940.21441-1-jasowang@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'drivers/net/caif/caif_virtio.c')
0 files changed, 0 insertions, 0 deletions