Date: Sat, 23 Dec 2000 00:00:21 -0800 (PST) From: Matt Dillon <dillon@earth.backplane.com> To: Assar Westerlund <assar@FreeBSD.ORG> Cc: mjacob@feral.com, current@FreeBSD.ORG Subject: Re: is it possible to have a NULL procp for an NFS request? Message-ID: <200012230800.eBN80Le93546@earth.backplane.com> References: <Pine.BSF.4.21.0012222323430.74029-100000@beppo.feral.com> <5lu27vlgz0.fsf@assaris.sics.se>
next in thread | previous in thread | raw e-mail | index | archive | help
:Matthew Jacob <mjacob@feral.com> writes:
:> Hmm. The client wasn't following symlinks.
:
:You sure? What happens is when you queue up an nfs operation provoked
:by following a symlink. I couldn't figure any other way of making
:that happen.
:
:> The patch seems simple enough, but it probably shouldn't just
:> swallow the error.
:
:Yeah, your patch to subr_prf.c is better.
:
:/assar
Looking at the cvs logs it looks like Poul forgot to check for
p == NULL in his new simplified tprintf() API. The 'sess' based
tprintf did check for NULL. The proc based tprintf does not.
So fixing it in tprintf() itself, in subr_prf.c, is the right move.
-Matt
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?200012230800.eBN80Le93546>