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.

Add basic support for FUSE_SYNCFS request
    
Honor the expected behavior of syncfs() to synchronously flush all data and metadata to disk on linux systems.

The kernel support was added in BZ 2185834

Hi,
For this backport, QE intend to do a tier 1 test(high priority level), do you think is it enough to verify this bug? Thanks.

(In reply to xiagao from comment #3)
> Hi,
> For this backport, QE intend to do a tier 1 test(high priority level), do
> you think is it enough to verify this bug? Thanks.

Yes, I think it's enough. Thanks

Hi Jon,

I see a new qemu-kvm build come out, and i guess the 'Fixed In Version' is 'qemu-kvm-6.2.0-35.module+el8.9.0+19024+8193e2ac'.
Am i right ?   Could you please add the accurate build nvr ? Thanks!

Best regards
Yanan Fu

Hi Jon,
This bug's status is ON-QA for some days, could you give an internal fixed version so that QE can do verify work?
Thanks.

According to comment4, I run a test loop and the result is pass.
http://virtqetools.lab.eng.pek2.redhat.com/kvm_autotest_job_log/?jobid=8010281 
So verify this bug.

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