On Fri, 2007-01-05 at 10:00 -0500, Shaya Potter wrote: > I'd agree with you (And even told the person the problem up front) > except it's not oopsing on a lack of intent information, it's oopsing > because nd is null and therefore can not access nd->mnt. > i.e. Let say I couldn't reconstruct nd perfectly (due to not knowing > vfsmnt information), I could possible construct a fake nd with the > proper intent information (i.e. very likely no intent information to be > passed) and it would still oops. No. The nameidata structure is _mandatory_, as is the intent info. In order to ensure POSIX correctness, the NFS client sometimes needs to create submounts (when crossing a mountpoint on the server). If you don't provide a proper nameidata structure, then that is impossible. Trond - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
