Bug 510809
Summary: | readlink cannot handle recursive symlinks | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Jeff Bastian <jbastian> | ||||
Component: | coreutils | Assignee: | Ondrej Vasik <ovasik> | ||||
Status: | CLOSED ERRATA | QA Contact: | qe-baseos-daemons | ||||
Severity: | urgent | Docs Contact: | |||||
Priority: | urgent | ||||||
Version: | 5.3 | CC: | asersen, jscotka, jwest, kdudka, syeghiay, tao | ||||
Target Milestone: | rc | Keywords: | ZStream | ||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | coreutils-5.97-25.el5 | Doc Type: | Bug Fix | ||||
Doc Text: |
When a directory contained a symbolic link to itself, the readlink command incorrectly gave the following error message: "Too many levels of symbolic links". With this update, the readlink command is able to correctly resolve values of recursive symbolic links to directories and no error messages are given.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2011-07-21 10:33:50 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: | |||||||
Bug Depends On: | |||||||
Bug Blocks: | 567545 | ||||||
Attachments: |
|
Description
Jeff Bastian
2009-07-10 21:15:15 UTC
Created attachment 351304 [details]
patch to fix readlink
I've backported the changes from upstream to use seen_triple() instead of cycle_check().
This request was evaluated by Red Hat Product Management for inclusion, but this component is not scheduled to be updated in the current Red Hat Enterprise Linux release. If you would like this request to be reviewed for the next minor release, ask your support representative to set the next rhel-x.y flag to "?". pm_ack for RHEL 5.4.z. (In reply to comment #1) > Created an attachment (id=351304) [details] > patch to fix readlink The patch looks good and solves the problem for me. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: When a directory contained a symbolic link to itself, the readlink command incorrectly gave the following error message when attempting to read the value of the symbolic link : "Too many levels of symbolic links". With this update, readlink is once again able to correctly resolve the value of the recursive symbolic links to containing directories, or "directory loops". Technical note updated. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1 @@ -When a directory contained a symbolic link to itself, the readlink command incorrectly gave the following error message when attempting to read the value of the symbolic link : "Too many levels of symbolic links". With this update, readlink is once again able to correctly resolve the value of the recursive symbolic links to containing directories, or "directory loops".+When a directory contained a symbolic link to itself, the readlink command incorrectly gave the following error message: "Too many levels of symbolic links". With this update, the readlink command is able to correctly resolve values of recursive symbolic links to directories and no error messages are given. An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1074.html An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2011-1074.html |