Bug 160097 - 2 issues with linux-2.6.11-exec-shield.patch in 1.33 kernel
2 issues with linux-2.6.11-exec-shield.patch in 1.33 kernel
Product: Fedora
Classification: Fedora
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Dave Jones
Brian Brock
Depends On:
  Show dependency treegraph
Reported: 2005-06-10 14:54 EDT by H.J. Lu
Modified: 2015-01-04 17:20 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-05 02:38:48 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description H.J. Lu 2005-06-10 14:54:10 EDT
linux-2.6.11-exec-shield.patch has

--- linux/include/asm-x86_64/processor.h.orig
+++ linux/include/asm-x86_64/processor.h
@@ -164,6 +164,15 @@ static inline void clear_in_cr4 (unsigne
 #define TASK_SIZE      (0x800000000000UL)

+#define TASK_SIZE_64   (0x800000000000)
+#define TASK_SIZE (test_thread_flag(TIF_IA32) ? IA32_PAGE_OFFSET : TASK_SIZE_64)
+extern unsigned long arch_align_stack(unsigned long sp);
 /* This decides where the kernel will search for a free chunk of vm
  * space during mmap's.

It leads to

In file included from include/linux/spinlock.h:16,
                 from include/linux/capability.h:45,
                 from include/linux/sched.h:7,
                 from init/calibrate.c:7:
include/asm/processor.h:169:1: warning: "TASK_SIZE" redefined
include/asm/processor.h:165:1: warning: this is the location of the previous

What is wrong with `UL'? Shouldn't the first "TASK_SIZE" be deleted?
Comment 1 Warren Togami 2005-06-10 15:57:04 EDT
What version of the FC3 kernel are you comparing this to?
Comment 2 H.J. Lu 2005-06-10 16:00:18 EDT
I saw it in today's 2.6.11-1.33_FC3.
Comment 3 Dave Jones 2005-06-10 17:50:47 EDT
fixed in CVS, will be in .34 later today

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