Bug 1967914
Summary: | [virtio-fs] virtiofsd quit when coping file to a folder in virtio-fs mounted volume(windows guest) | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 8 | Reporter: | xiagao |
Component: | qemu-kvm | Assignee: | Hanna Czenczek <hreitz> |
qemu-kvm sub component: | virtio-fs | QA Contact: | xiagao |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | kkiwi, lijin, virt-maint |
Version: | 8.5 | Keywords: | Triaged |
Target Milestone: | beta | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Windows | ||
Whiteboard: | |||
Fixed In Version: | qemu-kvm-4.2.0-53.module+el8.5.0+11673+72138537 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2021-11-09 18:01:39 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
xiagao
2021-06-04 12:08:33 UTC
Max, is this something you can have a look on? I don’t know, to be honest I have never run Windows inside qemu ever so far. I don’t even know where I’d get a Windows guest. The only thing that comes to my mind is that perhaps something wasn’t in our seccomp allowlist that should be there. I do remember 63659fe74e76f5c5285466f0c5cfbdca65b3688e adding fchmod() to the seccomp list, which could be invoked from SETATTR. Could you perhaps test for me whether the packages from https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37332956 fix the problem? (In reply to Max Reitz from comment #3) > Could you perhaps test for me whether the packages from > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37332956 fix the > problem? Xia Gao, any updates? (In reply to Klaus Heinrich Kiwi from comment #4) > (In reply to Max Reitz from comment #3) > > Could you perhaps test for me whether the packages from > > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37332956 fix the > > problem? > > Xia Gao, > > any updates? Sorry to reply late as I'm PTO and have some holiday. Yes, it works with https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37332956. qemu-kvm version: qemu-kvm-4.2.0-51.module+el8.5.0+10875+d90dbc7e.hreitz202106090942.x86_64 (In reply to xiagao from comment #5) > Yes, it works with > https://brewweb.engineering.redhat.com/brew/taskinfo?taskID=37332956. > > qemu-kvm version: > qemu-kvm-4.2.0-51.module+el8.5.0+10875+d90dbc7e.hreitz202106090942.x86_64 Great, thanks! Test pass with qemu-kvm-4.2.0-53.module+el8.5.0+11673+72138537.x86_64 Change status to verify. QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass. Verified with qemu-kvm-4.2.0-53.module+el8.5.0+11673+72138537.x86_64 according to comment0 remove SanityOnly flag. 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 (Moderate: virt:rhel and virt-devel:rhel security, 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/RHSA-2021:4191 |