Martin Pieuchot wrote: > On 08/11/19(Fri) 17:54, Martin Pieuchot wrote: > > uvm_mapanon() is called in two occasions: mmap(2) and sigaltstack(2). > > Both code paths are obviously in process context an can sleep. That > > explains why none of them set the UVM_FLAG_TRYLOCK when calling such > > function. > > > > The diff below removes support for this flag. This introduces a > > difference with uvm_map(9) but simplifies the overall code. Removing > > support for an unneeded "try" variant also means the lock can be grabbed > > earlier. This is a requirement to not lose atomicity between > > uvm_mapanon() and uvm_map_pageable() in mmap(2). > > Anyone?
yeah, this is partly why mapanon was split into another function, so we could remove the cruft that makes it complicated. go ahead.
