> From: Michael S. Tsirkin
> Sent: Monday, July 19, 2021 5:37 PM
>
> On Mon, Jul 19, 2021 at 05:44:49AM +, Parav Pandit wrote:
> >
> >
> > > From: Michael S. Tsirkin
> > > Sent: Sunday, July 18, 2021 2:17 AM
> > >
> > > On Sat, Jul 17, 2021 at 10:42:58AM +0300, Parav Pandit wrote:
> > > >
On Mon, Jul 19, 2021 at 05:44:49AM +, Parav Pandit wrote:
>
>
> > From: Michael S. Tsirkin
> > Sent: Sunday, July 18, 2021 2:17 AM
> >
> > On Sat, Jul 17, 2021 at 10:42:58AM +0300, Parav Pandit wrote:
> > > When a virtio pci device undergo surprise removal (aka async removaln
> > > in
> >
On Sat, Jul 17 2021, "Michael S. Tsirkin" wrote:
> On Sat, Jul 17, 2021 at 10:42:58AM +0300, Parav Pandit wrote:
>> When a virtio pci device undergo surprise removal (aka async removaln in
>
> typo
>
>> PCIe spec), mark the device is broken so that any upper layer drivers can
>> abort any
> From: Michael S. Tsirkin
> Sent: Sunday, July 18, 2021 2:17 AM
>
> On Sat, Jul 17, 2021 at 10:42:58AM +0300, Parav Pandit wrote:
> > When a virtio pci device undergo surprise removal (aka async removaln
> > in
>
> typo
Fixing it. Checkpatch.pl and codespell, both didn't catch it.
>
> OK
On Sat, Jul 17, 2021 at 10:42:58AM +0300, Parav Pandit wrote:
> When a virtio pci device undergo surprise removal (aka async removaln in
typo
> PCIe spec), mark the device is broken so that any upper layer drivers can
> abort any outstanding operation.
>
> When a virtio net pci device undergo
When a virtio pci device undergo surprise removal (aka async removaln in
PCIe spec), mark the device is broken so that any upper layer drivers can
abort any outstanding operation.
When a virtio net pci device undergo surprise removal which is used by a
NetworkManager, a below call trace was
