Bug 103717
Summary: | lockf function doesn't comply with Single Unix Specification | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 2.1 | Reporter: | Unai Uribarri Rodríguez <uribarri_u> |
Component: | kernel | Assignee: | Jim Paradis <jparadis> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 2.1 | CC: | peterm |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i686 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-06-08 21:39:05 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
Unai Uribarri Rodríguez
2003-09-04 08:53:23 UTC
The glibc version is glibc-2.2.4-26. glibc lockf just calls fcntl in the kernel. if we change this, we change behavior to userspace, which is something we don't want within a stable product release. It isn't needed to change the kernel. You can call traslate the negative length in lockf to a negative start and a positive length to fcntl, for example: struct flock flock; /* ... */ if (len < 0) { flock.l_start = len flock.l_len = -len; } else { flock.l_start = 0; flock.l_len = len; } RHEL2.1 is currently accepting only critical security fixes. This issue is outside the current scope of support. |