linux-kernel - [rfc 0/2] Introducing VmFlags field into smaps output

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: <20121022191452.785366817@openvz.org>
Date:	Mon, 22 Oct 2012 23:14:52 +0400
From:	Cyrill Gorcunov <gorcunov@...nvz.org>
To:	linux-kernel@...r.kernel.org
Cc:	Pavel Emelyanov <xemul@...allels.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Subject: [rfc 0/2] Introducing VmFlags field into smaps output

Hi guys, during c/r sessions we've found that there is no way at
the moment to fetch some VMA associated flags, such as mlock()
and madvise(), thus the patches in this series intorduce new field
into "smaps" output called VmFlags where all flags associated with
the particular VMA is shown in two letter mnemonic.

Strictly speaking for c/r we only need mlock/madvise bits but it
has been said that providing just a few flags looks somehow inconsistent.
So all flags are here now.

Please review. Comments and complains are quite welcome!

Thanks,
	Cyrill
--
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/