On Tue, 16 Jul 2013, Andrew Morton wrote:
> On Sun, 14 Jul 2013 18:54:51 +0200 Oleg Nesterov wrote:
>
> > mmap() doesn't allow the non-anonymous mappings with VM_GROWS* bit set.
> > In particular this means that mmap_region()->vma_merge(file, vm_flags)
> > must always fail if vm_flags &
On Tue, 16 Jul 2013, Andrew Morton wrote:
On Sun, 14 Jul 2013 18:54:51 +0200 Oleg Nesterov o...@redhat.com wrote:
mmap() doesn't allow the non-anonymous mappings with VM_GROWS* bit set.
In particular this means that mmap_region()-vma_merge(file, vm_flags)
must always fail if vm_flags
On Sun, 14 Jul 2013 18:54:51 +0200 Oleg Nesterov wrote:
> mmap() doesn't allow the non-anonymous mappings with VM_GROWS* bit set.
> In particular this means that mmap_region()->vma_merge(file, vm_flags)
> must always fail if vm_flags & VM_GROWS. So it does not make sense to
> check VM_GROWS*
On Sun, 14 Jul 2013 18:54:51 +0200 Oleg Nesterov o...@redhat.com wrote:
mmap() doesn't allow the non-anonymous mappings with VM_GROWS* bit set.
In particular this means that mmap_region()-vma_merge(file, vm_flags)
must always fail if vm_flags VM_GROWS. So it does not make sense to
check
mmap() doesn't allow the non-anonymous mappings with VM_GROWS* bit set.
In particular this means that mmap_region()->vma_merge(file, vm_flags)
must always fail if vm_flags & VM_GROWS. So it does not make sense to
check VM_GROWS* after we already allocated the new vma, the only caller,
mmap() doesn't allow the non-anonymous mappings with VM_GROWS* bit set.
In particular this means that mmap_region()-vma_merge(file, vm_flags)
must always fail if vm_flags VM_GROWS. So it does not make sense to
check VM_GROWS* after we already allocated the new vma, the only caller,
6 matches
Mail list logo