Bug 40360

Summary: Change (type foo *)0 to NULL in the NFS{Client,Server} code
Product: Base System Reporter: Hiten Pandya <hiten>
Component: kernAssignee: Peter Wemm <peter>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 5.0-CURRENT   
Hardware: Any   
OS: Any   
Attachments:
Description Flags
nfsnull.patch none

Description Hiten Pandya 2002-07-08 23:40:01 UTC 
	The NFS code in -CURRENT makes use of the old style way of refering
	to a null pointer, e.g. so = (struct socket *)0;, which should now be
	changed to use the NULL entity, e.g. so = NULL;

	I have produced a set of patches which fixes the above issue.  This
	information has been verified over IRC and Email so I am sure it is
	something that needs to be fixed.

	The Patch is also available from:
	http://www.unixdaemons.com/~hiten/work/diffs/nfsnull.patch

	Please do not hesistate to contact me for more information regarding
	this issue.

	P.S. This patches do _NOT_ need to be MFC'ed.
	
	Thank You.
		
		Hiten Pandya
		http://www.unixdaemons.com/~hiten
		hiten@{unixdaemons.com,uk.FreeBSD.org}

Fix: Apply the patches provided below and live happily ever after. :-)
How-To-Repeat: 	Check the NFS Server and Client code in -CURRENT.
Comment 1 Robert Watson freebsd_committer freebsd_triage 2002-07-10 02:44:20 UTC 
Responsible Changed
From-To: freebsd-bugs->peter

Peter last tore up the NFS code.
Comment 2 Matt Dillon freebsd_committer freebsd_triage 2002-07-11 18:49:09 UTC 
State Changed
From-To: open->closed

Manually applied patch and committed to -current on request by author.