grsecurity forums

Hello,

I use davinci kernel 2.6.33.rc4 (not from GIT but from Davinci released tree), and patched it with grsecurity-2.2.2-2.6.32.43-201107191826.patch. I did got some rejects (a list of about 10 files), and then when running the kernel I get kernel panic, init not found , syncing error message. I also tried to patch the same davinci kernel ( 2.6.33.rc4 ) with the most recent test patch grsecurity-2.2.2-2.6.39.3-201107191826.patch, but then the compilation is failed (it shouts about sched.h - it seems that symbol __rcu is not founded).
I would appreciate your guidance,

Best Regards,

Ran

ranshalit wrote:I use davinci kernel 2.6.33.rc4 (not from GIT but from Davinci released tree), and patched it with grsecurity-2.2.2-2.6.32.43-201107191826.patch. I did got some rejects (a list of about 10 files), and then when running the kernel I get kernel panic, init not found , syncing error message. I also tried to patch the same davinci kernel ( 2.6.33.rc4 ) with the most recent test patch grsecurity-2.2.2-2.6.39.3-201107191826.patch, but then the compilation is failed (it shouts about sched.h - it seems that symbol __rcu is not founded).

i don't know what the davinci kernel is but i can tell you that we no longer support such old kernels and that a given grsec patch applies to a specific kernel version only, not something that old. so your best course of action is to get this davinci kernel forward ported to 2.6.39.3 and then try to merge grsec into that (which itself may or may not be trivial).

Hi,

Thanks for the answer, I would like to know by general if the grsecurity patch applies to all kind of architecures (x86, davinci (TI), etc.) , or should be applied only to specific architecture, such as maybe x86.
Thank you very much,

Ran

PaX Team wrote:

ranshalit wrote:I use davinci kernel 2.6.33.rc4 (not from GIT but from Davinci released tree), and patched it with grsecurity-2.2.2-2.6.32.43-201107191826.patch. I did got some rejects (a list of about 10 files), and then when running the kernel I get kernel panic, init not found , syncing error message. I also tried to patch the same davinci kernel ( 2.6.33.rc4 ) with the most recent test patch grsecurity-2.2.2-2.6.39.3-201107191826.patch, but then the compilation is failed (it shouts about sched.h - it seems that symbol __rcu is not founded).

i don't know what the davinci kernel is but i can tell you that we no longer support such old kernels and that a given grsec patch applies to a specific kernel version only, not something that old. so your best course of action is to get this davinci kernel forward ported to 2.6.39.3 and then try to merge grsec into that (which itself may or may not be trivial).

In addition to my previous reply, I would like to add that "davinci" term refers to TI's cpu family, such as OMAP-L138. TI kernel for davinci can be doanloded from TI web sites (http://processors.wiki.ti.com/index.php/DaVinci_(ARM9)_PSP_Releases) and therfore I do not use the kernel GIT tree.

Regards,

Ran

ranshalit wrote:I would like to know by general if the grsecurity patch applies to all kind of architecures (x86, davinci (TI), etc.) , or should be applied only to specific architecture, such as maybe x86.

the patch itself contains everything we provide, there're no split out patches for different features/archs/etc. however not all features are implemented for all archs, the best supported arch is x86, everything else usually has the basic userland protection stuff as much as the CPU permits (i.e., non-exec pages and ASLR), but kernel self-protection is pretty much x86-only so far (REFCOUNT/sparc64 being the exception).