Hello all,
I was working on the 2.6 kernel (2.6.37) and I have just downloaded
the 3.13 Linux release and noticed that sys_fork(), sys_vfork(),
sys_clone() are no longer defined in arch/kernel/process.c
I have done some searches into the kernel and through the changelogs
of the different
Hello,
I am trying to boot a custom linux-2.6.37 port, but I am stuck at the
point where the kernel launches /init executable (since the initial
filesystem was mounted with initramfs support).
After investigations, it appears that a problem occurs during
prepare_binprm() function.
This function
hi,
Does your kernel config set this option:
CONFIG_EXT2_FS_XATTR=y
The result is the same with and without CONFIG_EXT2_FS_XATTR enabled.
And what is the state of CONFIG_AUDIT option? Do you need Kernel Audit
support in your environment?
CONFIG_AUDIT is disabled in my config.
A priori, I
so may be its not getxattr, but inode itself is null:
No, the inode is not NULL, it has been allocated in ram at adress 0x4654a0
and most of fields have been initialized.
For example:
d_inode-i_op-setattr = ramfs_nommu_setattr
d_inode-i_op-getattr = simple_getattr
There are other options like
Hello all,
What is the purpose of the inode-i_op-getxattr method?
During the boot of linux-2.6.37 on a new architecture, it crashes in the
get_vfs_caps_from_disk() function because of the following security check,
(in my case, this field is ot initialized).
if (!inode || !inode-i_op-getxattr)
Mulyadi Santosa mulyadi.sant...@gmail.com
Hi...
On Mon, Sep 24, 2012 at 9:58 PM, stl st.lamber...@gmail.com wrote:
Hello all,
What is the purpose of the inode-i_op-getxattr method?
I think it has something related to extended attribute
During the boot of linux-2.6.37 on a new
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:
sys_execve()
|- do_execve()
|- prepare_binprm()
|-security_bprm_set_creds()
Hello all,
if I try to boot Linux 2.6.37 by supplying a configuration file to the
kernel to create initramfs_data.cpio,
(without any compression), is it normal that the kernel doesn't print the
well known message:
VFS: Mounted root (type filesystem)
even if the boot reaches the point where it
30, 2012 at 8:10 PM, stl st.lamber...@gmail.com wrote:
Hello all,
if I try to boot Linux 2.6.37 by supplying a configuration file to the
kernel to create initramfs_data.cpio,
(without any compression), is it normal that the kernel doesn't print the
well known message:
VFS: Mounted root
); ---this
printk(KERN_WARNING Failed to execute %s\n,
ramdisk_execute_command);
}
instead of this:
run_init_process(/sbin/init);
run_init_process(/etc/init);
run_init_process(/bin/init);
run_init_process(/bin/sh);
is it normal?
Thanks!
2012/8/30 stl st.lamber...@gmail.com
Thanks for your answer.
Ok, here is what I have exactly done:
- compiled with my uClibc cross-compiler a simple hello world program.
- written a basic config file in linux-2.6.37/usr, creating a dev/console,
a /init from /usr/hello and some other dirs.
- edited the .config file with
To be more precise, all the content of the .init section will be freed at
the end of the boot. (see vmlinux.lds.S)
This is done by the function free_initmem() which is an architecture
specific function defined in linux-*/arch/arch/mm/init.c.
This function frees the memory between the symbols
sorry for the wrong manipulation
(resume of the previous mail)
As explained before, the symbols and functions defined with __init are only
used during boot initialization.
Thez will never be used again.
So The entire .init section is freed, and this freed memory will become
available memory pages
Hello all,
I need some explanations concerning the ways to mount rootf during boot.
I have read some documents (notably the very useful How to use initramfs by
Rob Landley)
and dug into the source code, but some doubts remain.
If I well understood, there is 2 differents procedures to mount the
Hello all,
I'm building a linux system for a new architecture,
and I want to use initramfs support to build a filesystem.
I have seen that there are several ways to do that with initramfs.
Either the kernel will build the cpio archive for me, or I can provide an
external one with the
Hello all,
I am porting linux-2.6.37 to a new architecture, and I am facing the
well-known problem:
VFS: Cannot open root device (null) or unknown-block(0,0)
When I was working on uClinux, the vmlinux image was concatenated with the
romfs image.
The kernel was aware of the address of the magic
16 matches
Mail list logo
