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.

Description of problem:
User haven't write access (can't write/create files, can't create folders) after switch to another user and switch back to original user.

Version-Release number of selected component (if applicable):
virtio-win-0.1.221

How reproducible:
100%

Steps to Reproduce:
1. Run VirtIO-FS as a Windows service
2. Switch to another user
3. Switch back to original user

Actual results:
User has read access but no write access

Expected results:
User has the same set of accesses as before switches.

Additional info:
Processing of UID/GID change after session change is broken.

Upstream PR to fix this issue:
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/803

Please check with the drivers from build 223 available at
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2109262

As having the same issue with https://bugzilla.redhat.com/show_bug.cgi?id=2042247#c3 ,set 'Assigned' status.

https://github.com/virtio-win/kvm-guest-drivers-windows/pull/810

the fix included in build 226
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=2176313

Try build 226.
Can't access the shared volume in guest(attachment), so reassign back.

Hi Vadim,

I think there is a missing commit from the build: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/810/commits/a1f9fea1f38eb90ae9475e2592680018ea609b08
from PR: https://github.com/virtio-win/kvm-guest-drivers-windows/pull/810

The new build should include the fix: virtio-win-prewhql-0.1-227

Test virtio-win-prewhql-0.1-227 on win2022 guest, it works well.

Verify steps:
1. start virtiofs service on win2022 and get a volume letter.
2. create a new user.
3. sign out and enter the new user created in step2.
4. check the shared dir, it still existed and could read/write in the shared dir.

So change the status to verified.

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-2023:2451