google/gvisor

Expand RLIMIT_DATA to enforce .data + .bss in addition to heap

Open

#156 opened on Mar 25, 2019

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Go (12,713 stars) (1,061 forks)batch import
area: mmexportedgood first issuepriority: p2type: bugtype: cleanup

Description

Presently, MemoryManager.Brk only enforces RLIMIT_DATA for the heap because .data and .bss information isn't plumbed from the loader.

Contributor guide

Tech stack
go
Domain
backendsecurityperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
gVisor memory managementloader and .data/.bssRLIMIT DATAGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30
Research direction
Examine MemoryManager.Brk in the mm package to understand current RLIMIT DATA enforcement. Investigate how the loader handles .data and .bss segments but does not expose their sizes. Design a method to plumb these sizes to MemoryManager.Brk so that the limit check includes both heap and static data. Review any existing discussions or linked PRs for context.