On 2 Feb 2015, Trond Myklebust verbalised: > Hmm... I'm at a loss to see how rpcb_create can ever call > rpc_new_client() with a null value for the nodename with that patch > applied. Are you 100% sure that the above Oops came from a patched > kernel? That IP address of "rpc_new_client+0x13b/0x1f2" looks > identical to the one in your original posting. I've been swapping kernels a lot of late due to bisection -- it is perfectly possible that I somehow ended up running an unpatched one :/ I'll do a build from scratch with the patch and reboot into it. My apologies if this was a false positive (which it looks quite like it might have been: your evidence is pretty persuasive!) -- NULL && (void) -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
