Hi, On 11 Dec 2013, at 19:11, Al Viro <viro@xxxxxxxxxxxxxxxxxx> wrote: > On Wed, Dec 11, 2013 at 10:49:29PM +0300, Vyacheslav Dubeyko wrote: >> This feature worked earlier under Linux. So, I suppose that some changes in HFS+ driver >> or in VFS broke it. And it needs to investigate and fix the reported issue. Thank you for the >> report. > > This "feature" is severely broken and yes, outright removal is what I'd > suggest for a fix. HFS+ allows hardlinks to files, which means that > you allow multiple dentries for the same inode with ->lookup() in it, > which is asking for deadlocks. > > This is fundamentally not supported. Considering that forks are lousy > idea in the first place, I'd seriously suggest to remove that idiocy for > good. Completely agree with Al. If anyone really wants access to forks they can implement them via the xattr interface (ok it has the 64k limitation but most forks are quite small so not much of an issue). That's how I implemented access to named streams in Tuxera NTFS and it works a treat (and allows Linux apps and various security modules that require xattr support to work properly which is also great). Best regards, Anton -- Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @) Unix Support, Computing Service, University of Cambridge J.J. Thomson Avenue, Cambridge, CB3 0RB, UK _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
