Messages in this thread | | | Date | Fri, 13 May 2011 10:31:22 -0400 | Subject | Re: [PATCH] nfs: check a crash in nfs_lookup_revalidate | From | Peng Huang <> |
| |
I did not write any code to call lookup_one_len(). I just mounted an ecryptfs on nfs, and then got the oops. So it should be a problem in nfs or ecryptfs or both. At least it should not crash.
Peng
On Fri, May 13, 2011 at 6:32 AM, Christoph Hellwig <hch@infradead.org> wrote: > On Wed, May 11, 2011 at 05:03:25PM -0400, Peng Huang wrote: >> lookup_one_len() may call nfs_loopup_revalidate() with nd == NULL >> indirectly, that causes the kernel crash. > > lookup_one_len must only be called by a filesystem or a library function > called by the filesystem. You are not allowed to call it on a random > filesystem like nfs that doesn't support the underlying assumptions. > > -- 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/
| |