Bug 184223
Summary: | File locking via fcntl() broken for NFS mounts in RHEL4u2 | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Steve Dickson <steved> |
Component: | kernel | Assignee: | Steve Dickson <steved> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 4.0 | CC: | gug, jbaron, maarten, mattdm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-06-20 16:03: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: | |
Embargoed: |
Description
Steve Dickson
2006-03-07 14:52:40 UTC
So, this works fine in RHEL 5 but still seems to be a problem on 4. Will a fix be forthcoming? Thanks. I'm not sure if I'm seeing a similar problem on my RHEL4.6 system. Kernel: 2.6.9-67.0.4.ELhugemem #1 SMP Fri Jan 18 05:11:24 EST 2008 i686 athlon i386 GNU/Linux strace: clone(Process 23784 attached child_stack=0, flags=CLONE_CHILD_CLEARTID|CLONE_CHILD_SETTID|SIGCHLD, child_tidptr=0xf6fda708) = 23784 [pid 23783] close(1) = 0 [pid 23783] close(2) = 0 [pid 23783] time(NULL) = 1216299609 [pid 23783] wait4(-1, Process 23783 suspended <unfinished ...> [pid 23784] open("/opt/applogs/rad/ac_data/log/ac.lock", O_WRONLY) = 3 [pid 23784] fcntl64(3, F_SETLKW, {type=F_WRLCK, whence=SEEK_CUR, start=0, len=0} The process hangs at this point. Thank you for submitting this issue for consideration in Red Hat Enterprise Linux. The release for which you requested us to review is now End of Life. Please See https://access.redhat.com/support/policy/updates/errata/ If you would like Red Hat to re-consider your feature request for an active release, please re-open the request via appropriate support channels and provide additional supporting details about the importance of this issue. |