All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anil Kumar" <anilk@subexgroup.com>
To: <kiran.thirumalai@in.ibm.com>, <linux-kernel@vger.kernel.org>
Subject: RE: Validating dynamically allocated kernel memory
Date: Mon, 11 Jun 2001 18:24:39 +0530	[thread overview]
Message-ID: <NEBBIIKAMMOCGCPMPBJOIEAKCFAA.anilk@subexgroup.com> (raw)
In-Reply-To: <CA256A68.00412D66.00@d73mta01.au.ibm.com>

try "sys_mprotect" with neccessary bit patterns set i.e, read/write/exec
type of protection check.

anil

-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of
kiran.thirumalai@in.ibm.com
Sent: Monday, June 11, 2001 5:12 PM
To: linux-kernel@vger.kernel.org
Subject: Validating dynamically allocated kernel memory


Hi,
Is there some kernel api to validate memory allocated using kmalloc.
Suppose, I allocate some memory using kmalloc and at a later point of
execution
I would like to validate if the memory allocated is not possibly freed by
some other thread.

Pls suggest a patch/pointers if any.
I also noticed a commented 'CONFIG_DEBUG_MALLOC' config option  (2.4.3
source),
It doesn't seem to be functional.  Any pointers towards the history behind
it would also be helpful.

Thanks in advance,
Kiran

PS: My previous post went through minus subject due to oversight
:-(...Apologising and resending ....


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



      reply	other threads:[~2001-06-11 12:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 11:41 Validating dynamically allocated kernel memory kiran.thirumalai
2001-06-11 12:54 ` Anil Kumar [this message]

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=NEBBIIKAMMOCGCPMPBJOIEAKCFAA.anilk@subexgroup.com \
    --to=anilk@subexgroup.com \
    --cc=kiran.thirumalai@in.ibm.com \
    --cc=linux-kernel@vger.kernel.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.