| Summary: | open() of existing file with O_EXCL on NFS filesystems incorrectly succeeds immediately after mounting filesystem | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Marc Riddle <mriddle> | ||||
| Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Red Hat Kernel QE team <kernel-qe> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.4 | CC: | bfields, dhowells, jlayton, rwheeler, sprabhu, steved | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2011-10-03 12:30:25 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
|
Description
Marc Riddle
2011-09-30 17:19:02 UTC
Created attachment 525802 [details]
reproducer for o_excl bug
Looking at the release notes of the most recent kernel package, I found: 2011-07-21 12:00:00 Frantisek Hrbata <fhrbata> [2.6.32-131.10.1.el6]: - [fs] NFS: Fix NFSv3 exclusive open semantics (Jeff Layton) [719925 694210] along with this in the errata notes: This update fixes a regression in which a client would use an UNCHECKED NFS CREATE call when an oen system call was attempted with the O_EXCL|O_CREAT flag combination. An EXCLUSIVE NFS CREATE call should have been used instead to ensure that O_EXCL semantics were preserved. As a result, an application could be led to believe that it had created the file when it was in fact created by anyother application. I'm installing this package now, but expect it to resolve my issue. Unfortunately the two bugzilla bugs referenced in the changelog are not visible to me, so when I searched for a similar bug I was unable to find one. Please let us know how the testing goes, thanks! *** This bug has been marked as a duplicate of bug 694210 *** |