linux-kernel - No more bits in vm_area_struct's vm

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <4AB9A0D6.1090004@crca.org.au>
Date:	Wed, 23 Sep 2009 14:15:18 +1000
From:	Nigel Cunningham <ncunningham@...a.org.au>
To:	LKML <linux-kernel@...r.kernel.org>
Subject: No more bits in vm_area_struct's vm_flags.

Hi all.

With the addition of the VM_MERGEABLE flag to vm_flags post-2.6.31, the
last bit in vm_flags has been used.

I have some code in TuxOnIce that needs a bit too (explicitly mark the
VMA as needing to be atomically copied, for GEM objects), and am not
sure what the canonical way to proceed is. Should a new unsigned long be
added? The difficulty I see with that is that my flag was used in
shmem_file_setup's flags parameter (drm_gem_object_alloc), so that
function would need an extra parameter too..

Regards,

Nigel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/