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
> > fun
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 remove
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
