From mboxrd@z Thu Jan 1 00:00:00 1970 From: Shaya Potter Subject: Re: nfs and printk's Date: Thu, 04 Nov 2004 13:20:35 -0500 Message-ID: <1099592435.5999.6.camel@dent> References: <1099535189.27369.4.camel@dent> <1099592258.11255.6.camel@lade.trondhjem.org> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: Linux Filesystem Development Return-path: Received: from opus.cs.columbia.edu ([128.59.20.100]:41102 "EHLO opus.cs.columbia.edu") by vger.kernel.org with ESMTP id S262358AbUKDSUq (ORCPT ); Thu, 4 Nov 2004 13:20:46 -0500 To: Trond Myklebust In-Reply-To: <1099592258.11255.6.camel@lade.trondhjem.org> Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2004-11-04 at 10:17 -0800, Trond Myklebust wrote: > on den 03.11.2004 Klokka 21:26 (-0500) skreiv Shaya Potter: > > is there any reason why printk's I'm putting in nfs_readdir() don't > > appear at all (when other's, such as in nfsd) do appear. If it matters, > > this is a 2.4.23 kernel. Is printk somehow defined out in fs/nfs/ ? > > printk() should always work. Just make sure that you are not confusing > it with "dprintk()". I'm not, but there's something else screwed up with my build. none of the printk's I'm adding now are doing anything. very weird, probably a stupid screw up on my part. thanks. shaya