Linux 2.6.28 Porting to Oxnas

This forum is for all other ARMv5 devices

Re: Linux 2.6.28 Porting to Oxnas

Postby ftcodes » Sun Jan 22, 2012 12:58 am

I tried to find something via google but looks like to be platform specific. Otherwise, something should have shown up more easily.

Solution for setuid problem:

$this->bbcode_second_pass_code('', '
sysctl -w vm.mmap_min_addr=32768
')

source: http://plugcomputer.org/plugforum/index ... pic=4879.0
ftcodes
 
Posts: 49
Joined: Fri Dec 30, 2011 5:49 pm

Re: Linux 2.6.28 Porting to Oxnas

Postby WarheadsSE » Sun Jan 22, 2012 3:42 am

:facepalm:

I've been looking for an answer for a week. Dammit. My googlefu is weakening

In the .config:
Kernel Features > default mmap min addr ( CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 )

I have patched both defconfigs, as this is where they had it set.
Core Developer
Remember: Arch Linux ARM is entirely community donation supported!
WarheadsSE
Developer
 
Posts: 6807
Joined: Mon Oct 18, 2010 2:12 pm

Re: Linux 2.6.28 Porting to Oxnas

Postby ftcodes » Sun Jan 22, 2012 8:26 am

$this->bbcode_second_pass_quote('WarheadsSE', ':')facepalm:

I've been looking for an answer for a week. Dammit. My googlefu is weakening

In the .config:
Kernel Features > default mmap min addr ( CONFIG_DEFAULT_MMAP_MIN_ADDR=65536 )

I have patched both defconfigs, as this is where they had it set.


It was already set in my config (but to that 65536 value). I got the issue, so I put that sysctl in sysctl.conf.

I have made that test binary to have enough specific words to find something. ;)

NB: On my system, I disabled that proled stuff since I got the /sys/class/leds support and it was pointing to the wrong GPIOs anyways.

I check that variable with the 32768 value. Seems the kernel 3.1 does not like the 65536.

Update: CONFIG_DEFAULT_MMAP_MIN_ADDR=32768 is the correct line and it works without sysctl.

The value can be lowered to 4096 which was the value within 2.6.31 kernels.
ftcodes
 
Posts: 49
Joined: Fri Dec 30, 2011 5:49 pm

Re: Linux 2.6.28 Porting to Oxnas

Postby elazar » Mon Jan 23, 2012 5:39 pm

Spent two days trying to figure out why sudo/su died with SIGKILL as well, found the same link a day or two ago. Time to rebuild my kernel...
elazar
 
Posts: 15
Joined: Mon Jan 16, 2012 7:07 pm

Previous

Return to Community Supported

Who is online

Users browsing this forum: No registered users and 37 guests