253733 – Cant build hardened gcc 4.3.2-r2 with hardened gcc 3.4.6-r2

Bug 253733 - Cant build hardened gcc 4.3.2-r2 with hardened gcc 3.4.6-r2

Summary: Cant build hardened gcc 4.3.2-r2 with hardened gcc 3.4.6-r2

Status:	RESOLVED FIXED

Alias:	None

Product:	Gentoo Linux
Classification:	Unclassified
Component:	Hardened (show other bugs)
Hardware:	All Linux

Importance:	Normal major (vote)
Assignee:	The Gentoo Linux Hardened Team

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2009-01-04 15:45 UTC by Alexey Shvetsov
Modified:	2009-01-25 04:10 UTC (History)
CC List:	6 users (show)

See Also:
Package list:
Runtime testing required:	---

Attachments
build log (build.log,1.75 MB, text/plain) 2009-01-04 15:46 UTC, Alexey Shvetsov	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexey Shvetsov archtester

2009-01-04 15:45:57 UTC

Cant build hardened gcc 4.3.2-r2 with hardened gcc 3.4.6-r2 on new system installed from official hardened stage3

Comment 1 Alexey Shvetsov archtester

2009-01-04 15:46:39 UTC

Created attachment 177354 [details]
build log

Comment 2 Alexey Shvetsov archtester

2009-01-04 15:47:06 UTC

bash segfaults while building gcc

Comment 3 Andrew Gaffney (RETIRED) gentoo-dev

2009-01-04 21:01:51 UTC

This isn't the universal experience. My upgrade from gcc-3.4.6-hardened to gcc-4.3.2-hardened was like a dream. The only thing that might make a difference is that my system was ~arch to begin with.

Comment 4 Andrew Gaffney (RETIRED) gentoo-dev

2009-01-05 16:15:44 UTC

I did another test in a chroot created from the stage3-amd64-2008.0-hardened tarball. It also worked just fine.

In the chroot, I did nothing other than change the profile from hardened/linux/amd64/2008.0 to hardened/amd64/multilib, add p.keywords entries for gcc-4.3.2-r2 and glibc-2.8_p20080602-r1, and then 'emerge -1 portage sys-devel/gcc'.

What profiles are people with failures using?

Comment 5 Gordon Malm (RETIRED) gentoo-dev

2009-01-21 00:21:31 UTC

hardened-sources-2.6.25-r13 and hardened-sources-2.6.26-r9 have been added to the tree and should fix this issue.  There is not a fixed 2.6.27 release at this time.  Please give them a try and report back.

Leaving the bug open until:
1. Confirmation of fix.
2. A fixed 2.6.27 release is in the tree.
3. At least one of the fixed releases has been marked stable.

Thanks to all who reported and helped to figure out in which release we regressed.

Reference bug #254843

Comment 6 Gordon Malm (RETIRED) gentoo-dev

2009-01-21 08:07:33 UTC

Adding PaX Team to CC.

PaX Team: I believe the root cause of this is the same as Bug #254843.

Comment 7 PaX Team 2009-01-21 09:49:57 UTC

(In reply to comment #6)
> Adding PaX Team to CC.
> 
> PaX Team: I believe the root cause of this is the same as Bug #254843.

yes, it probably is, it happened to me as well just last night when i was trying to rebuild an amd64 partition i managed to nuke the other day. same request for help applies as well, a kernel stack dump when that piece of stack expansion code is triggered.

Comment 8 Gordon Malm (RETIRED) gentoo-dev

2009-01-24 16:33:25 UTC

sys-kernel/hardened-sources-2.6.27-r5 has been added to the tree with the fix for this bug.

Comment 9 Gordon Malm (RETIRED) gentoo-dev

2009-01-25 04:10:24 UTC

Closing as fixed, re-open if you hit the bug with any kernels currently in the portage tree.  Will pursue the bug further with PaX Team.  If anyone else wants to help reproduce the bug with pax-2.6.28.1-test9 and provide the PaX Team the requested info feel free to post it here.