Joerg Wunsch f7d5a5328f When encountering a ISO_SUSP_CFLAG_ROOT element in Rock Ridge ... processing, this actually means there's a double slash recorded in the symbolic link's path name. We used to start over from / then, which caused link targets like ../../bsdi.1.0/include//pathnames.h to be interpreted as /pathnahes.h. This is both contradictionary to our conventional slash interpretation, as well as potentially dangerous. The right thing to do is (obviously) to just ignore that element. bde once pointed out that mistake when he noticed it on the 4.4BSD-Lite2 CD-ROM, and asked me for help. Reviewed by: bde (about half a year ago) MFC after: 3 days		2006-03-13 22:32:33 +00:00
..
cd9660_bmap.c
cd9660_iconv.c
cd9660_lookup.c	Apply the same fix to a potential race in the ISDOTDOT code in	2005-10-16 21:41:54 +00:00
cd9660_mount.h
cd9660_node.c	I ran into an nfs client panic a couple of times in a row over the	2006-01-17 17:29:03 +00:00
cd9660_node.h
cd9660_rrip.c	When encountering a ISO_SUSP_CFLAG_ROOT element in Rock Ridge	2006-03-13 22:32:33 +00:00
cd9660_rrip.h
cd9660_util.c
cd9660_vfsops.c	Normalize a significant number of kernel malloc type names:	2005-10-31 15:41:29 +00:00
cd9660_vnops.c	Add marker vnodes to ensure that all vnodes associated with the mount point are	2006-01-09 20:42:19 +00:00
iso_rrip.h
iso.h	Implement the full range of ISO9660 number conversion routines in iso.h.	2005-10-18 13:35:08 +00:00
TODO
TODO.hibler