On Wed, Jan 30, 2002 at 12:32:17PM -0700, Jon Arney wrote:
> In __hurd_file_name_lookup_retry, there seems to be a test for recursion
> in the form of:
>
> switch (doretry)
> {
> case FS_RETRY_REAUTH:
> if (err = reauthenticate (*result))
> return err;
Marcus Brinkmann wrote:
>
> It should definitely fail with ELOOP.
I aggree.
>
> The bug is probably in glibc/sysdeps/mach/hurd/access.c, which is the
> implementation of access() on the Hurd. That would be a good place to
> start your research. (Could also be in the file name lookup itself,
On Wed, Jan 30, 2002 at 10:21:26AM -0700, Jon Arney wrote:
> The upshot of the whole
> thing is that if you call access() on a recursive link,
> the /hurd/auth process goes nuts!
> I think this is a really neat feature of the 'access()' call and the
> behavior of the /hurd/auth daemon, but not ev
Hi.
In the course of "building my own" hurd system from the
sources, I came across an interesting "feature" of the
access() call. It happened accidentally, and took me a little
while to figure out what caused it, but I have an easily
reproducable test-case for it. The upshot of the whole
thing i
