Date: Sun, 4 Jan 2009 12:41:49 -0800 (PST)
From: Trent Piepho <xyzzy@speakeasy.org>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
cc: Linus Torvalds <torvalds@linux-foundation.org>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Harvey Harrison <harvey.harrison@gmail.com>,
       "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] printk: Let %pR handle NULL pointers
In-Reply-To: <1231062493.15389.105.camel@pasglop>
Message-ID: <Pine.LNX.4.58.0901041232460.25853@shell2.speakeasy.net>
References: <1230979341-23029-1-git-send-email-xyzzy@speakeasy.org> 
 <alpine.LFD.2.00.0901030905140.3179@localhost.localdomain> 
 <1231019614.15389.104.camel@pasglop>  <Pine.LNX.4.58.0901031827380.25853@shell2.speakeasy.net>
 <1231062493.15389.105.camel@pasglop>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1106
Lines: 20

On Sun, 4 Jan 2009, Benjamin Herrenschmidt wrote:
> > I thought of doing that too, but then all the various %pX formats would all
> > have to print the same for NULL pointers.  For instance a resource prints
> > out like "[0x1000-0x100f]", so I chose "[NULL]" for printing a null
> > resource pointer.  Maybe "[]" or "[-]" would be better?  A null MAC address
> > could be ":::::" or "x:x:x:x:x:x".  "N.U.L.L" or "x.x.x.x" for a null IP4
> > address.  And so on.  So the printout looks nicer when a NULL pointer isn't
> > a bug.
>
> And how often is that ?

For resource pointers it's not uncommon.  There are many cases when it's perfectly
ok for a resource pointer to be null, e.g. res->parent is often null, pci devices
and busses don't usually have all possible ranges, etc.  It nice to get decent info
printouts without having the check for NULL pointers.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/