Messages in this thread | | | Date | Wed, 6 Jan 2016 15:14:22 +0530 | Subject | Re: [PATCH 2/2] proc read mm's {arg,env}_{start,end} with mmap semaphore taken. | From | Anshuman Khandual <> |
| |
On Wed, Jan 6, 2016 at 10:32 AM, Mateusz Guzik <mguzik@redhat.com> wrote: > Only functions doing more than one read are modified. Consumeres > happened to deal with possibly changing data, but it does not seem > like a good thing to rely on.
There are no other functions which might be reading mm-> members without having a lock ? Why just deal with functions with more than one read ?
| |