Re: [gentoo-hardened] Kernel Oops at Boot with hardened-sources

[Charles Taylor]

Thanks!

Worked like a charm.

What is the purpose of DEBUG_RODATA?? It sounded like
a good idea when I read its description.

I will not pretend to have anything more than an
superficial understanding of the various protected
mode descriptor tables, I'm just curious.

--- pageexec@××××××××.hu wrote:

> On 18 Mar 2007 at 14:56, Charles Taylor wrote:
>
> > grsecurity and PaX are disabled and the same
> .config
> > that builds this disaster builds a perfectly
> working
> > kernel using gentoo-sources (2.6.19-gentoo-r5) on
> the
> > same machine.
>
> PaX changes certain things even without being
> explicitly
> enabled. among others, it makes some important data
> structures
> read-only. since you also enabled DEBUG_RODATA, the
> kernel
> will enforce it. the problem with that is that some
> of these
> data structures (in your case, the GDT) need to be
> written
> from time to time. PaX itself has special code that
> allows
> this when KERNEXEC is enabled (which is the feature
> that
> also enforces read-only data, among many other
> things). of
> course the special code isn't even compiled in when
> KERNEXEC
> is disabled, so you get an oops like this. the
> proper solution
> is to use KERNEXEC if you really want read-only
> kernel data,
> or disable DEBUG_RODATA.
>
> --
> gentoo-hardened@g.o mailing list
>
>

-- 
gentoo-hardened@g.o mailing list