Skip to contentSkip to conversation

nfs and printk's

DISCUSSION Shaya Potter 3 participants 4 messages Nov 4, 2004 VFS

lore
Share & tools
lore
#0 lore raw

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/ ?

thanks,

shaya

#1 lore raw

on den 03.11.2004 Klokka 21:26 (-0500) skreiv Shaya Potter:

Quoted 3 lines

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()".

Cheers,
Trond

Signature · 1 line
Trond Myklebust <[email protected]>
#2 lore raw
Quoted 7 lines · Trond Myklebust

on den 03.11.2004 Klokka 21:26 (-0500) skreiv Shaya Potter:

Quoted 3 lines

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

#3 lore raw
Quoted 8 lines · Shaya Potter
Quoted 6 lines · Trond Myklebust

on den 03.11.2004 Klokka 21:26 (-0500) skreiv Shaya Potter:

Quoted 3 lines

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/ ?

Quoted 7 lines
Quoted 2 lines

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.

It could also depend on the log level used in the printk() call. Are you using one (like KERN_DEBUG)?
If so, either don't use one (usually Works For Me) or increase the level of logging (Alt-SysRq-9).

Signature · 1 line
~Randy