Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 155962

Summary: Deprecate newlines in ext2/3 filenames
Product: [Fedora] Fedora Reporter: Need Real Name <lsof>
Component: e2fsprogsAssignee: Thomas Woerner <twoerner>
Status: CLOSED NOTABUG QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4CC: sct
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-26 10:48:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Need Real Name 2005-04-26 07:41:42 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050416 Epiphany/1.6.1

Description of problem:
Many people don't know that ext2/3 allows newlines in filenames.
Deprecating this would alert people to this and allow eventual removal.

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

How reproducible:

Steps to Reproduce:

Additional info:

Comment 1 Stephen Tweedie 2005-04-26 10:48:26 UTC
First of all, e2fsprogs has nothing to do with the live running ext3 filesystem:
mounted filesystems are all managed by the kernel, not by e2fsprogs.

But more importantly, the behaviour of filenames is thoroughly defined by Unix,
SingleUnix and POSIX standards.  There's no way ext3 is going to suddenly become
non-standards-compliant by implementing a feature like this.  The standards have
become fixed over time, and unfortunately, for better or worse, it's way too
late to start changing what counts as a legal filename or not.

I don't see it as much of a problem, though: most people won't ever encounter
this case.  Those who do either have a need for it, or they did it by accident.
 And there are certainly things we can do to make recovery from such accidents
painless, like making sure that Nautilus and KDE can browse, rename and delete
such files correctly.  But that's not a filesystem problem.