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:
This issue was uncovered in coverity scan of "RHBA-2017:27617-01
e2fsprogs bug fix and enhancement update". It's good to check return
value of a system call in code.
e2fsprogs-1.42.9/misc/filefrag.c:278
---
if (sync_file)
fsync(fd);
---
link to covscan page:
http://cov01.lab.eng.brq.redhat.com/covscanhub/waiving/et_mapping/18204/
No other fsync(2) calling doesn't check return value. This bug happens in e2fsprogs-1.42.9-10.el7, not in e2fsprogs-1.42.9-9.el7. It exists in upstream code since 2012.
Version-Release number of selected component (if applicable):
e2fsprogs-1.42.9-10.el7
How reproducible:
always
Steps to Reproduce:
run coverity scan against e2fsprogs
Actual results:
calling fsync(2) doesn't check return value
Expected results:
calling fsync(2) checks return value
Additional info:
N/A
It's not really new in 1.42.9-10, it's just that the /other/ fsyncs got fixed in 1.42.9-10, and so now Coverity notices the remaining outlier.
There's really no reason to push this into 7.4 at the last minute, IMHO, so pushing it out to 7.5 (and I'll leave it to Lukas' discretion for that)
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, 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-2019:2176
Description of problem: This issue was uncovered in coverity scan of "RHBA-2017:27617-01 e2fsprogs bug fix and enhancement update". It's good to check return value of a system call in code. e2fsprogs-1.42.9/misc/filefrag.c:278 --- if (sync_file) fsync(fd); --- link to covscan page: http://cov01.lab.eng.brq.redhat.com/covscanhub/waiving/et_mapping/18204/ No other fsync(2) calling doesn't check return value. This bug happens in e2fsprogs-1.42.9-10.el7, not in e2fsprogs-1.42.9-9.el7. It exists in upstream code since 2012. Version-Release number of selected component (if applicable): e2fsprogs-1.42.9-10.el7 How reproducible: always Steps to Reproduce: run coverity scan against e2fsprogs Actual results: calling fsync(2) doesn't check return value Expected results: calling fsync(2) checks return value Additional info: N/A