On Thu, Oct 8, 2020 at 7:23 PM Matthew Wilcox <[email protected]> wrote: > On Thu, Oct 08, 2020 at 07:13:51PM +0200, Jann Horn wrote: > > And for expanding stacks, it might be a good idea for other > > reasons as well (locking consistency) to refactor them such that the > > size in the VMA tree corresponds to the maximum expansion of the stack > > (and if an allocation is about to fail, shrink such stack mappings). > > We're doing that as part of the B-tree ;-) Although not the shrink > stack mappings part ...
Wheee, thanks! Finally no more data races on ->vm_start?
