-
Bug
-
Resolution: Unresolved
-
Normal
-
rhel-9.5
-
No
-
Moderate
-
CustomerScenariosInitiative
-
rhel-sst-virtualization-windows
-
ssg_virtualization
-
8
-
QE ack
-
False
-
-
Yes
-
Red Hat Enterprise Linux
-
None
-
None
-
None
-
Unspecified Release Note Type - Unknown
-
-
x86_64
-
Windows
-
None
What were you trying to do that didn't work?
Opening a mounted virtiofs share in Windows Explorer with a self-symlink inside will cause the guest's virtiofs driver to crash.
Please provide the package NVR for which bug is seen:
5.14.0-494.el9.x86_64
virtiofsd-1.11.1-1.el9.x86_64
virtio-win-prewhql-0.1-262
Win11 23h3(os build 22631.3447)
How reproducible:
100%
Steps to reproduce
1. Create virtiofsd with root privilege:
mkdir /root/avocado/data/avocado-vt/virtio_fs_test/ &
/usr/libexec/virtiofsd --socket-path=/var/tmp/avocado-vt-vm1-fs-virtiofsd.sock -o source=/root/avocado/data/avocado-vt/virtio_fs_test/ -o cache=auto &
2.Create a self-symlink for a file
ln -s tmp tmp
lrwxrwxrwx 1 root root 6 Sep 18 08:34 tmp-link.sh -> tmp.sh
3. Start Win11 guest and start virtiofs.exe
C:\>virtios.exe
4. In Windows Explorer open the drive mounted with virtiofs (in my case drive Z) and the virtiofs.exe will crash.
Expected results
virtiofs.exe will not crash and possibly show the offending self-symlink as a shortcut.
Actual results
The virtiofs.exe crashed.
Event 1000 detailed info is in attachment.