Linus Torvalds writes: (Summary) Side note: doing some grepping, I find some other sequences that are a bit
scary, like this:
scary, like this:
arch/x86/kernel/acpi/wakeup_32.S-.data
arch/x86/kernel/acpi/wakeup_32.S-ALIGN
arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_magic) .long 0 arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_eip) .long 0 arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_eip) .long 0 so apparently people are using ENTRY() for data too (the same pattern exists in wakeup_64.S).
exists in wakeup_64.S).
So we end up having those odd 0x90 bytes (now 0xcc) in the data section as "padding" between those two values.
scary, like this:
arch/x86/kernel/acpi/wakeup_32.S-.data
arch/x86/kernel/acpi/wakeup_32.S-ALIGN
arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_magic) .long 0 arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_eip) .long 0 arch/x86/kernel/acpi/wakeup_32.S:ENTRY(saved_eip) .long 0 so apparently people are using ENTRY() for data too (the same pattern exists in wakeup_64.S).
exists in wakeup_64.S).
So we end up having those odd 0x90 bytes (now 0xcc) in the data section as "padding" between those two values.