Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Hi Xiaoling,
This is the problem (error: -9):
[2022-03-28T07:39:37Z DEBUG virtiofsd::server] Received request: 29
[2022-03-28T07:39:37Z DEBUG virtiofsd::server] Replying ERROR, header: OutHeader { len: 16, error: -9, unique: 447 }
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (virtio-win bug fix and enhancement update), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2022:8261
Description of problem: During CreateDirectory handling (WinAPI call) WinFSP submits 'Create' and then 'Close' operations to the service. On 'Close' the service submits FUSE_RELEASEDIR message to the host with invalid file handle (-1) because directory has never opened (FUSE_MKDIR only creates directory). How reproducible: 100% Steps to Reproduce: 1. Create new directory with WinAPI's CreateDirectory 2. Check virtiofsd-rs output Actual results: // InHeader { len: 57, opcode: 9 (FUSE_MKDIR), unique: 889, nodeid: 1, uid: 1000, gid: 1000, pid: 8, padding: 0 } Replying OK, header: OutHeader { len: 144, error: 0, unique: 889 } // InHeader { len: 64, opcode: 29 (FUSE_RELEASEDIR), unique: 890, nodeid: 16, uid: 0, gid: 0, pid: 8, padding: 527 } Replying ERROR, header: OutHeader { len: 16, error: -9, unique: 890 } Expected results: CreateDirectory should not cause virtiofsd-rs ERROR reply.