Skip to content

Conversation

@ioannisg
Copy link
Member

@ioannisg ioannisg commented Jun 11, 2019

When building without support for user mode (CONFIG_USERSPACE=n)
we need to correct the starting address of the MPU Guard, before
passing it to the function that evaluates whether a stack
corruption has occurred. The bug was introduced by 60bae5d in
#13619, where the start address of the MPU guard was properly
corrected, but the guard start at the corresponding stack-fail
check was not adjusted accordingly.

Signed-off-by: Ioannis Glaropoulos [email protected]

@ioannisg ioannisg added bug The issue is a bug, or the PR is fixing a bug area: ARM ARM (32-bit) Architecture area: Memory Protection labels Jun 11, 2019
@ioannisg ioannisg requested a review from galak as a code owner June 11, 2019 19:14
@ioannisg ioannisg added the priority: low Low impact/importance bug label Jun 11, 2019
@ioannisg ioannisg added this to the 2.0 milestone Jun 11, 2019
@ioannisg
Copy link
Member Author

I would back-port that to 1.14.1

@ioannisg ioannisg force-pushed the arch_arm_mpu_fix_guard_limit_no_usermode branch from 235d499 to 0f97fe4 Compare June 11, 2019 19:17
@nashif
Copy link
Member

nashif commented Jun 12, 2019

@ioannisg if this is going into 1.14.1, please create a bug

When building without support for user mode (CONFIG_USERSPACE=n)
we need to correct the starting address of the MPU Guard, before
passing it to the function that evaluates whether a stack
corruption has occurred. The bug was introduced by commit
(60bae5d) in
PR-13619, where the start address of the MPU guard was properly
corrected, but the guard start at the corresponding stack-fail
check was not adjusted accordingly.

Signed-off-by: Ioannis Glaropoulos <[email protected]>
@ioannisg ioannisg force-pushed the arch_arm_mpu_fix_guard_limit_no_usermode branch from 0f97fe4 to a6c834e Compare June 12, 2019 08:07
@ioannisg ioannisg modified the milestones: 2.0, v2.0.0 Jun 12, 2019
@ioannisg
Copy link
Member Author

@ioannisg if this is going into 1.14.1, please create a bug

@nashif @MaureenHelm , pls, take a look at the associated bug report: #16779

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area: ARM ARM (32-bit) Architecture area: Memory Protection bug The issue is a bug, or the PR is fixing a bug priority: low Low impact/importance bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants