Date: Sun, 17 Dec 2000 21:58:04 -0800 From: Doug Barton <DougB@gorean.org> To: assar@FreeBSD.ORG Cc: Bosko Milekic <bmilekic@technokratis.com>, John Baldwin <jhb@FreeBSD.ORG>, freebsd-current@FreeBSD.ORG Subject: Re: Panic with fairly up to date -current, seems NFS related Message-ID: <3A3DA76B.FB6944B4@gorean.org> References: <Pine.BSF.4.21.0012172119180.430-100000@jehovah.technokratis.com> <5ly9xe8o03.fsf@assaris.sics.se>
next in thread | previous in thread | raw e-mail | index | archive | help
assar@FreeBSD.ORG wrote: > > Bosko Milekic <bmilekic@technokratis.com> writes: > > I'm more concerned with whether it's actually normal for the process > > pointer to be NULL in the first place. Is this the case? > > One example (which I don't know if that what's happening here) is when > following symbolic links. namei() calls VOP_READLINK with proc == NULL. What a coincidence, there is a symbolic link involved here. I have a workstation, and a gateway/fileserver machine. I export /usr on the fileserver (slave) and use amd to mount individual directories under /usr in /mnt/slave/ on the workstation. Scattered throughout the workstation are symbolic links to /mnt/slave/foo, which kick amd in gear, and make those directories available where I want them. I realize that this is not an ideal situation, but it's also very common, so if someone is going to find a bug this way, it might as well be me. :) Doug -- "The most difficult thing in the world is to know how to do a thing and to watch someone else do it wrong without comment." -- Theodore H. White Do YOU Yahoo!? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A3DA76B.FB6944B4>