> so may be its not getxattr, but inode itself is null:<br><br>No, the inode is not NULL, it has been allocated in ram at adress 0x4654a0 and most of fields have been initialized.<br>For example:<br>d_inode->i_op->setattr = <ramfs_nommu_setattr><br>
d_inode->i_op->getattr = <simple_getattr><br><br>> There are other options like CONFIG_AUDIT_TREE, disable that too. Also<br>> make sure that initrd image has the ext2 driver compiled for this<br>
> kernel.<br><br>I am using initramfs support to mount VFS, not init ramdisk (initrd)<br>If I well understand, in my case I have not to deal with precompiled drivers.<br>I only provide a config file to the CONFIG_INITRAMFS_SOURCE option.<br>
<br><br>
> If you are using vanilla ext2 fs and CONFIG_EXT2_FS_XATTR is set, then<br>
> it must be initialized in static inode operations table, look at:<br>
> ext2_file_inode_operations for files<br>
> ext2_dir_inode_operations for dir<br>
> ext2_special_inode_operations for special files<br>
> ext2_fast_symlink_inode_<div id=":1mk">> operations and ext2_symlink_inode_operations<br>
> for symlinks<br>
> all of them are compiled and initialized with generic_getxattr if you<br>
> compile with CONFIG_EXT2_FS_XATTR.</div><br>Indeed, I dug in the source code, I agree with this.<br>Unfortunalety, when debugging, it appears that inode->i_op->getxattr remains null.<br><br>But I am confused.. for example, what the difference (in the .config file) between<br>
"File systems" and "Pseudo filesystems" menus?<br>Because we are speaking about my VFS, so at the moment, the kind of <br>the filesystem is not really important for me.<br>What the difference if I choose ramfs instead of ext2 for example? <br>
I have some shadow zones that make me confused..<br><br>Thanks for your help.<br><br>