getxattr field not initialized when trying to execute /init during boot
htmldeveloper at gmail.com
Wed Sep 26 11:57:40 EDT 2012
On Thu, Sep 13, 2012 at 5:08 PM, stl <st.lambert02 at gmail.com> wrote:
> Hello all,
> I am facing a problem when trying to boot linux 2.6.37 on a new architecture.
> At the end of the boot, it tries to launch /init by executing a sys_execve()
> Here is the what it does:
> |-> do_execve()
> |-> prepare_binprm()
> In the get_vfs_caps_from_disk(), these is a verification to know if inode->i_op->getxattr
> has been initialized.
> In my case, it returns and error value, because this field is not initialized.
> So I am wondering by who and where this field is initialized?
> And what is the aim of getxattr?
it is called extended attributes for filesystem:
(there is a detail explanation in above link as I copied it here):
+ * Extended attributes are stored on disk blocks allocated outside of
+ * any inode. The i_file_acl field is then made to point to this allocated
+ * block. If all extended attributes of an inode are identical, these
+ * inodes may share the same extended attribute block. Such situations
+ * are automatically detected by keeping a cache of recent attribute block
+ * numbers and hashes over the block's contents in memory.
and for security modules:
> Thanks in advance!
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
More information about the Kernelnewbies