Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 298471 - setfacl fails on long utf8 path
setfacl fails on long utf8 path
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: acl (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Jiri Moskovcak
Depends On:
  Show dependency treegraph
Reported: 2007-09-20 11:50 EDT by Jiri Moskovcak
Modified: 2015-02-01 17:47 EST (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2007-1033
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-21 07:03:38 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Proposed patch (650 bytes, patch)
2007-09-21 06:00 EDT, Jiri Moskovcak
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2007:1033 normal SHIPPED_LIVE acl bug fix update 2007-11-21 07:03:36 EST

  None (edit)
Description Jiri Moskovcak 2007-09-20 11:50:29 EDT
Description of problem:
setfacl is not able to handle output from getfacl when working with long UTF8 names.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. getfacl <long path with international characters in UTF8> > output.dump
2. setfacl --restore=output.dump
Actual results:
setfacl fails.

Expected results:
setfacl should read the output and restore acl for the file.

Additional info:
Comment 1 Jiri Moskovcak 2007-09-21 06:00:00 EDT
Created attachment 201831 [details]
Proposed patch
Comment 7 errata-xmlrpc 2007-11-21 07:03:38 EST
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 the 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.


Note You need to log in before you can comment on or make changes to this bug.