Re: [PATCH v2 0/3] virtiofs: hiprio FORGET robustness and no-reply request completion

[PATCH v2 0/3] virtiofs: hiprio FORGET robustness and no-reply request completion · Li Wang <hidden> · 2026-04-02
[PATCH v2 2/3] virtiofs: Retry hiprio FORGET when virtqueue_add_outbuf() returns -ENOMEM · Li Wang <hidden> · 2026-04-02
[PATCH v2 1/3] virtiofs: Complete no-reply virtio requests without parsing the out header · Li Wang <hidden> · 2026-04-02
[PATCH v2 3/3] virtiofs: Do not stall hiprio FORGET dispatch after dropping one request · Li Wang <hidden> · 2026-04-02
Re: [PATCH v2 0/3] virtiofs: hiprio FORGET robustness and no-reply request completion · Miklos Szeredi <miklos@szeredi.hu> · 2026-06-11
Re: [PATCH v2 0/3] virtiofs: hiprio FORGET robustness and no-reply request completion · Stefan Hajnoczi <hidden> · 2026-06-11

From: Miklos Szeredi <miklos@szeredi.hu>
Date: 2026-06-11 09:29:24
Also in: linux-fsdevel, lkml

On Thu, 2 Apr 2026 at 12:45, Li Wang [off-list ref] wrote:

This series fixes virtiofs completion for FUSE requests that do not use a
reply descriptor, tightens hiprio FORGET handling when virtqueue submission
fails transiently, and prevents the hiprio worker from stalling when one
FORGET must be dropped after an unrecoverable error.

Can someone from the virtiofs team please review this?

Thanks,
Miklos

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help