Attempting to print an object pointed to by a bad (usually ERR_PTR) pointer
is a not so surprising error. Our code handles them inconsistently:
* two places print (null) if ptr<PAGE_SIZE
* one place prints (null) if abs(ptr)<PAGE_SIZE
* one place prints (null) only if !ptr