grsecurity forums

by **PaX Team** » Tue Aug 15, 2006 12:50 pm

mtg wrote:Yes, I have console access. Is the email-address on pax.grsecurity.net the one?

yes.

As a sidenote: Here a 2.4.33-grsec SMP runs perfectly with UDEREF on a Single P4/HT.

i understand but it's a different box, i'd like exclude one variable on the box where UDEREF fails, that's why i thought of trying to boot with 1 CPU only. also, if you can irc, #grsecurity or #pax on oftc is a bit faster for communication ;-)

.

by **PaX Team** » Tue Aug 15, 2006 12:54 pm

aldee wrote:Unlike for the previous posters, I had to disable both new features, MEMORY_SANITIZE and UDEREF for the machine to boot properly. Well, actually I didn't check if it works if only UDEREF is enabled. It didn't work with only MEMORY_SANITIZE being enabled. Tested on a vanilla 2.4.33 kernel with only grsec patches applied.

sanitize failure is a new one, can you tell me what happens if you enable it? if it's an oops, i'd like to see it.

by **aldee** » Tue Aug 15, 2006 1:26 pm

PaX Team wrote:
aldee wrote:Unlike for the previous posters, I had to disable both new features, MEMORY_SANITIZE and UDEREF for the machine to boot properly. Well, actually I didn't check if it works if only UDEREF is enabled. It didn't work with only MEMORY_SANITIZE being enabled. Tested on a vanilla 2.4.33 kernel with only grsec patches applied.
sanitize failure is a new one, can you tell me what happens if you enable it? if it's an oops, i'd like to see it.

I have to retract my statement.

I don't know what I (or, possibly, my ISP's remote bootstrapping system) messed up, however, it does in fact work with SANITIZE being enabled now that I double checked it. Maybe I simply missed a make clean between tries ...

So, in fact, it's only UDEREF making trouble. Sorry.

by **PaX Team** » Wed Aug 23, 2006 7:39 pm

aldee wrote:So, in fact, it's only UDEREF making trouble. Sorry.

can you test the latest PaX test patch? it should fix the SMP boot issue but i don't know what else could go wrong on UP. this time at least you'll get a more meaningful error report, i'll need that and your System.map.

by **aldee** » Mon Aug 28, 2006 8:53 am

PaX Team wrote:
aldee wrote:So, in fact, it's only UDEREF making trouble. Sorry.
can you test the latest PaX test patch? it should fix the SMP boot issue but i don't know what else could go wrong on UP. this time at least you'll get a more meaningful error report, i'll need that and your System.map.

It looks like the SMP fix took care of my problem as well - even without SMP ...

Running 2.4.33.2-grsec with UDEREF enabled without problems.

Thanks for the quick fix,

aldee

grsecurity forums

2.4.33-grsec hangs on boot