On Thu, Jan 04, 2007 at 07:47:34PM -0500, Shaya Potter wrote: > yes, you're writing a stackable file system (the cs.sunysb gives that > away) and have run a lookup_one_len() on a nfs mounted file system and > that means nd is null. > > Erez's group is trying to fix that situation so the intents can be > passed correctly. If you look for the last Unionfs submission to lkml/fsdevel, one of the patches creates lookup_one_len_nd which allows you to pass a nameidata structure down to the lower filesystem. Beware, NFSv4 is cranky when it comes to lookup intents. In Unionfs, we have some additional lookup_one_len's in a number of places that have no nameidata that we can work off of, and that's causing quite a number of problems as NFSv4 gets confused when it doesn't see an intent. Josef "Jeff" Sipek. -- You measure democracy by the freedom it gives its dissidents, not the freedom it gives its assimilated conformists. - Abbie Hoffman - 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
