linux-kernel - efficient way to verify one memory block is only readable?

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>] [day] [month] [year] [list]

Message-ID: <56176AE6.30002@gmail.com>
Date:	Fri, 09 Oct 2015 15:21:10 +0800
From:	mudongliang <mudongliangabcd@...il.com>
To:	kernelnewbies@...nelnewbies.org
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: efficient way to verify one memory block is only readable?

When I did some experiments about vtable, and modified the virtual 
method address myself,
I found error report : "Segment fault". When I see the /proc/self/maps, 
vtable is in the readonly text segment.
I almost forget the fact that vtables have been stored in readonly segment.

So I have a question : how to effectively verify one memory block is 
only readable or writable?
I think it's not efficient to check all the parts in /proc/maps.
Does anyone have another efficient way to do this verification?

Thanks in advance.
     - mudongliang
--
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/