This is the mail archive of the
ecos-bugs@sourceware.org
mailing list for the eCos project.
[Issue 1000775] New: Hard links to directories
- From: bugzilla-daemon at ecoscentric dot com
- To: ecos-bugs at ecos dot sourceware dot org
- Date: Wed, 20 May 2009 12:47:24 +0100
- Subject: [Issue 1000775] New: Hard links to directories
http://bugzilla.ecoscentric.com/show_bug.cgi?id=1000775
Summary: Hard links to directories
Product: eCos
Version: CVS
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: normal
Component: Filesystem support
AssignedTo: jifl@ecoscentric.com
ReportedBy: wry@ecoscentric.com
QAContact: ecos-bugs@ecos.sourceware.org
Class: Advice Request
In working on YAFFS I found myself considering the question of hard links to
directories. Operating on the premise that such things are mind-bending
abominations, a nightmare to implement correctly, and in any event rarely
actually useful, I looked into whether or not we actually forbid them. Well,
fileio makes no attempt to off its own bat, but then for it to do so would be
expensive (add a call to stat within link?), so one would argue that it should
be up to the individual filesystems to check and enforce. (I'm going to forbid
them in YAFFS on the grounds that it asserted when I tried to rmdir such a
link, and I don't currently know enough about its internals to see whether this
is can be usefully supported in a reasonable time.)
Of the filesystems in eCos, romfs is obviously uninteresting, and fatfs doesn't
allow any links. The other two - ramfs and jffs2 - appear to make no attempt to
catch directory hard links, and I suspect that if somebody was ever to be mad
enough to try, they'd trip over all sorts of bugs. It should be pretty
straightforward to patch in such proscriptions, but before I do so I thought
I'd open this ticket in case anybody else wanted to comment...
--
Configure issuemail: http://bugzilla.ecoscentric.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the issue.