spender wrote:I didn't change anything in the patch you said fixed your problem that would have actually fixed your reported problem. Furthermore, all the changes contained between the patch you had problems with and the one that "fixed" it are contained in the 3.0.3 patch. I believe you have a broken toolchain/build environment.
thing is, you're the only one seeing this problem, so obviously there's something peculiar with your build environment. since we don't have access to it, only you can figure out what makes ssp enabled for your kernel compiles...simonbcn wrote:It's very curious that my "broken toolchain/build environment" only fails when I compile the kernel with your patches... Without your patches it compiles well...
PaX Team wrote:thing is, you're the only one seeing this problem, so obviously there's something peculiar with your build environment. since we don't have access to it, only you can figure out what makes ssp enabled for your kernel compiles...simonbcn wrote:It's very curious that my "broken toolchain/build environment" only fails when I compile the kernel with your patches... Without your patches it compiles well...
as i just learned from Kees Cook, ubuntu's gcc forcibly enables ssp so successful compilation under !CC_STACKPROTECTOR relies on the main Makefile disabling support for ssp explicitly. and which happens to be somewhat broken with the plugins as the cc-option target uses KBUILD_CFLAGS for no good reason i think. next patch will hopefully fix this, let me know if it doesn't.simonbcn wrote:And why when I compile without your patch compilation doesn't fail?