Skip to contentSkip to conversation

arm64: fix add kasan bug

PATCH New zhong jiang 1 participant 1 message Jan 16, 2016 3 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): 56982daf.v++3ELUdiwhIHn5Z%[email protected]

A message that is not in the archive (sent off-list or not yet received): CAPAsAGxqdm_ftXMebmg_R89ZScaaFzRuqRGV=eeKMrDLtn3DvA@mail.gmail.com

A message that is not in the archive (sent off-list or not yet received): [email protected]

#3 lore raw

PATCH 112/178 arm64: fix add kasan bug

Quoted 20 lines · Catalin Marinas
Quoted 19 lines · Andrey Ryabinin

2016-01-15 2:22 GMT+03:00 <[email protected]>:

Quoted 17 lines

From: zhong jiang <[email protected]>
Subject: arm64: fix add kasan bug

In general, each process have 16kb stack space to use, but stack need extra space to store red_zone when kasan enable. the patch fix above question.

Cc Andrey Ryabinin <[email protected]>
Cc Catalin Marinas <[email protected]>
Cc Xishi Qiu <[email protected]>
Cc Wang Long <[email protected]>

---

 arch/arm64/include/asm/thread_info.h |   15 +++++++++++++--
 1 file changed, 13 insertions(+), 2 deletions(-)
Quoted 9 lines
Quoted 2 lines

This has been nacked by Catalin:
http://lkml.kernel.org/g/<[email protected]>

As above, the patch doesn't make much sense for 4.5 where we have separate IRQ stacks. Arguably, it could be included in 4.4 *if* there was a regression but the patch author failed to reply.

Thanks.

I'm so sorry that I don't respond to this email in time, Because I thought it has been recognized without any discussion. and I am busy with other things during the time. at present, I have looked at all of the discussion, and I have some words want to say.

when kasan enables, compiler need to insert an additional 32-byte redzon to a local variable in the front and behind. as a result, The actual usable stack space is less than half of the total. The main purpose of this patch is whether kasan enable or not, the actual usable stack space always satisfied the demand to avoid the risk of the stack overflow.

Thanks
zhongjiang