On 09/05/2016 04:33 PM, Dmitry Safonov wrote:
Changes from v4:
- check both vm_ops and vm_private_data to avoid (unlikely) confusion
with some other vma in map_vdso_once (as Andy noticed) - which would
lead to unable to use this API in that unlikely-case
(vm_private_data may be
On 09/05/2016 04:33 PM, Dmitry Safonov wrote:
Changes from v4:
- check both vm_ops and vm_private_data to avoid (unlikely) confusion
with some other vma in map_vdso_once (as Andy noticed) - which would
lead to unable to use this API in that unlikely-case
(vm_private_data may be
Changes from v4:
- check both vm_ops and vm_private_data to avoid (unlikely) confusion
with some other vma in map_vdso_once (as Andy noticed) - which would
lead to unable to use this API in that unlikely-case
(vm_private_data may be uninitialized and be the same as vvar_mapping
or
Changes from v4:
- check both vm_ops and vm_private_data to avoid (unlikely) confusion
with some other vma in map_vdso_once (as Andy noticed) - which would
lead to unable to use this API in that unlikely-case
(vm_private_data may be uninitialized and be the same as vvar_mapping
or
4 matches
Mail list logo