Where exactly is the red zone on x86-64?

31
votes

From Wikipedia:

In computing, a red zone is a fixed-size area in a function's stack frame beyond the return address which is not preserved by that function. The callee function may use the red zone for storing local variables without the extra overhead of modifying the stack pointer. This region of memory is not to be modified by interrupt/exception/signal handlers. The x86-64 ABI used by System V mandates a 128-byte red zone, which begins directly after the return address and includes the function's arguments. The OpenRISC toolchain assumes a 128-byte red zone.

From the System V x86-64 ABI:

The 128-byte area beyond the location pointed to by %rsp is considered to be reserved and shall not be modified by signal or interrupt handlers. Therefore, functions may use this area for temporary data that is not needed across function calls. In particular, leaf functions may use this area for their entire stack frame, rather than adjusting the stack pointer in the prologue and epilogue. This area is known as the red zone.

  • Given these two quotes, is the red zone above the stacked return address or below the stacked return address?

  • Since this red zone is relative to RSP, does it move downward with each push and does it move upward with each pop?

2
assemblyx86-64calling-conventionabired-zone
maybe interesting? eli.thegreenplace.net/2011/09/06/stack-frame-layout-on-x86-64. It seems to clarify the issue? The stack grows 'downwards' (lower address) in memory. The 'red zone' is the area 'down' (lower memory address) from the current 'stack pointer'. – Ryan Vincent
Interesting indeed. As always: a picture is worth a thousand words! – Sep Roland
The description on Wikipedia sounds totally wrong. begins directly after the return address and includes the function's arguments is total nonsense. On function entry, %rsp points at the return address, so yes the red-zone begins below there until the function modifies %rsp. Args are above the return address. They're safe from async modification for the normal reason (being above %rsp), not because of the red zone. That part of the Wiki article is flat out wrong, and I don't see any valid interpretation. – Peter Cordes
@PeterCordes It's precisely that answer by Cody Gray that made me doubt because of the discrepancy between the negative offset (-8) to RSP and the comment for the 32-byte scratch area. I see you've bugfixed it. It makes sense now. – Sep Roland
@SepRoland: ouch. Documentation bugs can be really confusing. I'm kind of a fanatic about making sure answers don't include any wrong info, even if their answer to the main question is ok. (e.g. this inline asm that had unsafe constraints, where the only way to get my point through the OP's thick head was to write a whole answer.) Anyway, glad to hear that my attention to detail is justified. Too bad I didn't notice that earlier, since I'd already upvoted it soon after Cody posted it :) – Peter Cordes

2 Answers

23
votes

Given these two quotes, is the red zone above the stacked return address or below the stacked return address?

The red zone is the 128 bytes just below rsp, i.e. rsp - 128 to rsp - 1.

Since this red zone is relative to RSP, does it move downward with each push and does it move upward with each pop?

Yes.

9
votes

The Wikipedia article about the Red Zone was wrong, thus creating the ambiguity.

I had modified the article in April 2017 to fix the issue. As of that update the Wikipedia article reads:

In computing, a red zone is a fixed-size area in a function's stack frame beyond the current stack pointer which is not preserved by that function. The callee function may use the red zone for storing local variables without the extra overhead of modifying the stack pointer. This region of memory is not to be modified by interrupt/exception/signal handlers. The x86-64 ABI used by System V mandates a 128-byte red zone, which begins directly under the current value of the stack pointer. The OpenRISC toolchain assumes a 128-byte red zone

This brings the Wikipedia article more in line with the 64-bit System V ABI definition. With the ambiguity above resolved, regarding the question:

Since this red zone is relative to RSP, does it move downward with each push and does it move upward with each pop?

The Red Zone is always the 128 bytes just below RSP. As RSP changes (by PUSH/POP/MOV etc) so too does the location of the Red Zone.