Summary: | 2.4.28-grsec-2.1.0-pax-mmap-pgtables.patch failed when emerging hardened-sources-2.4.28-r5 | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Horst Prote <prote> |
Component: | [OLD] Core system | Assignee: | Andrea Luzzardi <scox> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | converter42, tocharian |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | The error file of the failed patch. |
Description
Horst Prote
2005-03-09 06:35:47 UTC
Created attachment 53011 [details]
The error file of the failed patch.
Maybe it's a matter of order of patches because I found the context lines of
the
last chunck of 2.4.28-grsec-2.1.0-pax-mmap-pgtables.patch in
3100_grsecurity-2.1.0-200501051112.patch
I don't know what has changed but during my "emerge sync; emerge -u world" yesterday hardened-sources-2.4.28-r5 installed without problem. This time the 2.4.28-grsec-2.1.0-pax-mmap-pgtables.patch was applied after all the other patches (unlike the last time; see my initial bug report):
>>> Preparing to unpack ...
>>> Unpacking source...
>>> Unpacking linux-2.4.28.tar.bz2 to /var/tmp/portage/hardened-sources-2.4.28-r5/work
* hardened-patches-2.4-28.5.tar.bz2 unpacked
* Excluding Patch #32... [ ok ]
* Applying 1000_patch-o-matic-ng.patch (-p0+)... [ ok ]
* Applying 1001_device-mapper.patch (-p0+)... [ ok ]
* Applying 1002_evms.patch (-p0+)... [ ok ]
* Applying 1003_xattr.patch (-p0+)... [ ok ]
* Applying 1004_proconfig.patch (-p0+)... [ ok ]
* Applying 1005_cryptoloop.patch (-p0+)... [ ok ]
* Applying 1006_squashfs2.1.patch (-p0+)... [ ok ]
* Applying 1007_wdt-fix.patch (-p0+)... [ ok ]
* Applying 1008_ebtables.patch (-p0+)... [ ok ]
* Applying 1009_fix-net-neighbor-backport.patch (-p0+)... [ ok ]
* Applying 2000_netdev-random-core.patch (-p0+)... [ ok ]
* Applying 2001_netdev-random-drviers.patch (-p0+)... [ ok ]
* Applying 3100_grsecurity-2.1.0-200501051112.patch (-p0+)... [ ok ]
* Applying 3101_grsecurity-secure-io.patch (-p0+)... [ ok ]
* Applying 3102_grsecurity-secure-kmem.patch (-p0+)... [ ok ]
* Applying 4000_CAN-2004-1137.patch (-p0+)... [ ok ]
* Applying 4001_CAN-2004-1056.patch (-p0+)... [ ok ]
* Applying 4002_CAN-2004-0814.patch (-p0+)... [ ok ]
* Applying 4003_CAN-2004-1074.patch (-p0+)... [ ok ]
* Applying 4004_CAN-2004-1058.patch (-p0+)... [ ok ]
* Applying 4005_CAN-2004-1016.patch (-p0+)... [ ok ]
* Applying 4006_CAN-2004-1235.patch (-p0+)... [ ok ]
* Applying 4007_random-poolsize.patch (-p0+)... [ ok ]
* Applying 4008_smp-page-fault-handler.patch (-p0+)... [ ok ]
* Applying 4009_CAN-2004-1333.patch (-p0+)... [ ok ]
* Applying 4010_CAN-2004-1335.patch (-p0+)... [ ok ]
* Applying 2.4.28-grsec-2.1.0-pax-mmap-pgtables.patch (-p0+)... [ ok ]
...
So for me the bug is fixed.
|