Bug#78678: hurd: symlink to empty name crashes libdiskfs

2000-12-04 Thread Marcus Brinkmann
On Sun, Dec 03, 2000 at 05:22:42PM -0500, Roland McGrath wrote: > That said, I hacked this patch, which might work. It does, with one small glitch: hurd:/mnt/x# ln -s "" foo hurd:/mnt/x# ls -l total 0 lrwxr-xr-x1 root root0 Dec 4 14:42 foo -> hurd:/mnt/x# ls foo ls: : No suc

Bug#78678: hurd: symlink to empty name crashes libdiskfs

2000-12-03 Thread Marcus Brinkmann
On Sun, Dec 03, 2000 at 05:22:42PM -0500, Roland McGrath wrote: > We should figure out what behavior we want. In Linux 2.2, it is impossible > to create a symlink with empty contents (symlink returns ENOENT). However, I verified that it doesn't crash when it finds one on a Hurd fs. It acts as a

Bug#78678: hurd: symlink to empty name crashes libdiskfs

2000-12-03 Thread Roland McGrath
We should figure out what behavior we want. In Linux 2.2, it is impossible to create a symlink with empty contents (symlink returns ENOENT). In FreeBSD 4.1, you can create a symlink to empty--and it acts like a symlink to /. What I would have expected was that it act like a symlink to ., but it

Bug#78678: hurd: symlink to empty name crashes libdiskfs

2000-12-03 Thread Marcus . Brinkmann
Package: hurd Version: N/A Severity: normal >From the TODO file: *** If the target of a symlink is the empty string, stat seems to spin forever !!! This is not true, instead it crashes with E_BAD_ACCESS. Here is what happens. Consider 'ln -s "" foo; cat foo' libdiskfs/dir-lookup.c: path is "f