All of lore.kernel.org
 help / color / mirror / Atom feed
* efficient way to verify one memory block is only readable?
@ 2015-10-09  7:21 ` mudongliang
  0 siblings, 0 replies; 2+ messages in thread
From: mudongliang @ 2015-10-09  7:21 UTC (permalink / raw)
  To: kernelnewbies

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

^ permalink raw reply	[flat|nested] 2+ messages in thread
* efficient way to verify one memory block is only readable?
@ 2015-10-09  7:21 ` mudongliang
  0 siblings, 0 replies; 2+ messages in thread
From: mudongliang @ 2015-10-09  7:21 UTC (permalink / raw)
  To: kernelnewbies; +Cc: linux-kernel@vger.kernel.org

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

^ permalink raw reply	[flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-10-09  7:21 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-10-09  7:21 efficient way to verify one memory block is only readable? mudongliang
2015-10-09  7:21 ` mudongliang

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.