From: Shaya Potter Subject: Re: Is a NULL check missing in nfs_lookup? Date: Thu, 04 Jan 2007 19:47:34 -0500 Message-ID: <1167958054.5190.1.camel@localhost.localdomain> References: Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: linux-fsdevel@vger.kernel.org Return-path: Received: from cs.columbia.edu ([128.59.16.20]:53339 "EHLO cs.columbia.edu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965112AbXAEAr5 (ORCPT ); Thu, 4 Jan 2007 19:47:57 -0500 To: Chaitanya Patti In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org 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. On Thu, 2007-01-04 at 19:00 -0500, Chaitanya Patti wrote: > > Hello everyone, > > In the function nfs_lookup in nfs/dir.c , the following line (line # 926): > > error = nfs_reval_fsid(nd->mnt, dir, &fhandle, &fattr); > > uses `nd' without having checked if it is NULL. > > Is this correct? > > This is in kernel version 2.6.19.1 > > Can someone check this ? > > Thanks, > > Chaitanya. > - > To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html