Re: [PATCH 1/3] fork/exec: cleanup mm initialization

On 06/19, Vladimir Davydov wrote: > > mm initialization on fork/exec is spread all over the place, which makes > the code look inconsistent. > > We have mm_init(), which is supposed to init/nullify mm's internals, but > it doesn't init all the fields it should: > > - on fork

[PATCH 1/3] fork/exec: cleanup mm initialization

mm initialization on fork/exec is spread all over the place, which makes the code look inconsistent. We have mm_init(), which is supposed to init/nullify mm's internals, but it doesn't init all the fields it should: - on fork ->mmap,mm_rb,vmacache_seqnum,map_count,mm_cpumask,locked_vm are

[PATCH 1/3] fork/exec: cleanup mm initialization

mm initialization on fork/exec is spread all over the place, which makes the code look inconsistent. We have mm_init(), which is supposed to init/nullify mm's internals, but it doesn't init all the fields it should: - on fork -mmap,mm_rb,vmacache_seqnum,map_count,mm_cpumask,locked_vm are

Re: [PATCH 1/3] fork/exec: cleanup mm initialization

On 06/19, Vladimir Davydov wrote: mm initialization on fork/exec is spread all over the place, which makes the code look inconsistent. We have mm_init(), which is supposed to init/nullify mm's internals, but it doesn't init all the fields it should: - on fork