All of lore.kernel.org
 help / color / mirror / Atom feed
From: mudongliangabcd@gmail.com (mudongliang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: efficient way to verify one memory block is only readable?
Date: Fri, 09 Oct 2015 15:21:10 +0800	[thread overview]
Message-ID: <56176AE6.30002@gmail.com> (raw)

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

WARNING: multiple messages have this Message-ID (diff)
From: mudongliang <mudongliangabcd@gmail.com>
To: kernelnewbies@kernelnewbies.org
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: efficient way to verify one memory block is only readable?
Date: Fri, 09 Oct 2015 15:21:10 +0800	[thread overview]
Message-ID: <56176AE6.30002@gmail.com> (raw)

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

             reply	other threads:[~2015-10-09  7:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-09  7:21 mudongliang [this message]
2015-10-09  7:21 ` efficient way to verify one memory block is only readable? mudongliang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56176AE6.30002@gmail.com \
    --to=mudongliangabcd@gmail.com \
    --cc=kernelnewbies@lists.kernelnewbies.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
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.